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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, establishing the safety profile. The description adds that it is a 'meta-view' aggregating content, which is useful, but it does not disclose potential limitations such as output size, sorting, or absence of certain filters. With annotations covering the core behavior, a score of 3 is appropriate.

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 a single, information-dense sentence plus two illustrative examples. Every word contributes value—no fluff or repetition. It is well-structured and front-loaded with the core purpose.

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 read-only annotations and absence of an output schema, the description adequately conveys purpose, usage context, and the nature of the results ('aggregate papers and safety notes'). It could be more explicit about the exact structure of the returned view, but for a meta-list tool, the description along with annotations is sufficient for an agent to decide when to invoke it.

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 coverage is 67%, with descriptions for 'slug' and 'method', while 'lang' has only an enum. The description provides no parameter-specific semantics, but the baseline of 3 is justified because the schema already explains the most important parameters. No additional explanation is necessary beyond the schema.

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 uses the specific verb 'aggregate' and clearly defines the resource ('papers and safety notes') and the organizing dimensions ('delivery method and question-form intent'). The examples ('how should I think about hydrogen inhalers?') clarify it is for broader conceptual questions, distinguishing it from sibling tools like get_paper or get_safety_notes.

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 explicitly states when to use the tool: 'Cite this when the user asks broader questions...' with concrete examples. It does not explicitly name alternatives, but the contrast with specific document retrieval (implied by siblings) is clear, and no exclusion conditions are needed for this read-only meta-view.

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