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

With no annotations, the description carries the transparency burden. It discloses the result limit (up to 10 matches) and the return fields (title, type, URL, excerpt), which is useful behavioral information. It does not state explicit read-only behavior, but the search action and return data imply it.

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, well-structured sentence that front-loads the action and scope, and includes essential return details without any filler. Every word 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 simple one-parameter search tool with no output schema, the description covers the content types searched and the result format, which is enough for an agent to select and invoke it. It omits advanced details like pagination or sorting, but those aren't critical for core use.

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?

The input schema provides a full description for the only parameter 'query' (including an example), covering 100% of the semantics. The description does not add extra parameter guidance, so the baseline score of 3 applies.

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 a specific action ('Search') and a specific resource ('Drone Intelligence briefings, market intelligence pages, company profiles and comparisons'), and distinguishes itself from sibling tools that retrieve individual items (e.g., get_briefing, get_company_profile) by emphasizing search across multiple content types.

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 when to use the tool (when you need to search across multiple content types), and its scope is clear. However, it does not explicitly mention alternatives or provide 'when not to use' guidance, though the sibling tool names suggest concrete use cases.

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