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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint. The description adds valuable context: the data is 'locally collected' (not real-time), includes 'original URLs', and has a 'reported/verified distinction' – all beyond what annotations convey. No contradictions.

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?

A single, tightly worded sentence (15 words) that front-loads the action and resource. Every phrase adds meaningful distinction; no redundancy or filler.

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 tool has 4 optional parameters and no output schema, the description is far from complete. It does not explain parameter semantics, response format, or how the 'reported/verified distinction' affects results. The agent cannot reliably construct a query without further information.

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% and the description mentions none of the four parameters (limit, query, source, category). With no parameter explanations in either the schema or description, agents have zero guidance on how to formulate a search, making the tool effectively opaque.

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 specific verb ('Search') and resource ('aerospace events'), and adds distinctive attributes ('locally collected', 'dated', 'original URLs', 'reported/verified distinction') that clearly differentiate it from sibling aerospace tools like aerospace_capability_signals or aerospace_glossary.

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 is clear about what it does but offers no guidance on when to use it vs alternatives, no mention of exclusions, and no hint at which sibling tools cover overlapping territory. The agent is left to infer usage solely from the resource name.

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