get_new_publications

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations are provided, so the description must fully disclose behavior. It states the tool retrieves publications but does not clarify whether the operation is read-only or if it has side effects (e.g., marking publications as read). The unread_only parameter suggests filtering, but the tool's impact on state is unclear.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is exceptionally concise with a clear purpose statement followed by a short, well-structured args list. Every sentence adds value, and there is no redundancy or unnecessary information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the presence of an output schema, the tool does not need to explain return values. The description adequately covers the parameters and basic purpose. However, it omits details like sort order (likely by date) and potential limitations (e.g., pagination beyond limit). For a simple retrieval, it is mostly complete.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description must add meaning. It explains each parameter: topic filters by tag (empty means all), limit caps results with default 20, unread_only returns only unread with default True. This adds value beyond the schema, though it lacks details on valid topic values or ordering.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool retrieves new publications, optionally filtered by topic. However, it does not explicitly differentiate from sibling tools like search_literature or search_library that also retrieve publications. The term 'new' is ambiguous but partially clarified by the unread_only parameter.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies use for retrieving new publications with optional filters, but it provides no explicit guidance on when to use this tool versus alternatives (e.g., search_literature). It also does not mention any prerequisites or context for usage.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.