Pubmed Summary

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

No annotations are provided, so the description carries the full burden. It discloses a useful operational constraint ('Up to 50 PMIDs per request') and a performance trait ('faster than pubmed_fetch'), but says nothing about read-only nature, authentication, or any other behavioral limits. The output schema covers return values, so that omission is acceptable.

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?

Two short sentences, front-loaded with the core purpose and the key constraint. No filler; every clause earns its place.

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?

For a single-parameter lookup tool with an output schema, the description covers the essential purpose, the main alternative, and the batch limit. It could be more complete by stating what a summary contains or whether it is purely read-only, but the output schema and simple schema reduce the burden.

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 compensate. It adds meaning by identifying the parameter as PMIDs and imposing a maximum of 50 per request, but it does not specify the string format, whether duplicates are allowed, or behavior on invalid IDs. Partial compensation only.

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 states a clear verb and resource ('Get concise summaries of articles') and distinguishes itself from pubmed_fetch by speed. It does not specify what the summary contains, but the purpose is unambiguous and an agent can tell it apart from the named sibling.

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 names pubmed_fetch as an alternative and implies this tool should be used when speed matters, but it does not explicitly state when to choose one over the other or any prerequisites. Usage is inferable rather than spelled out.

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