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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint, and destructiveHint=false, so the safety profile is fully covered. The description adds essentially nothing behavioral beyond that – no hint on result limits, ranking, pagination, or whether 'public' implies an unauthenticated lookup.

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?

One compact sentence with no filler. The tradeoff is that its brevity comes from under-specification rather than disciplined editing.

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?

An output schema exists, so return-value explanation is not required. However, with an undocumented query parameter and no routing guidance against four siblings, the definition is only minimally complete for an agent to select and invoke it correctly.

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 single required 'query' parameter has 0% schema description coverage and the description never explains what the query matches (rate names, geography, service type) or its format. A 300-character maxLength constraint is the only guidance, and that comes from the schema, not the text.

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?

States a verb+resource ('Search current public rate records'), but the qualifier 'for the desktop composer resource picker' is obscure UI jargon that doesn't sharpen the meaning. Nothing distinguishes it from siblings like search or compare_rates.

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?

No statement of when to use this versus compare_rates, search, or fetch, despite three plausible overlapping siblings. The only scoping signal is 'public' and 'current', which is implied rather than explained.

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