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

readOnlyHint=true already covers the safety profile, so the description's remaining job is to add behavior. It usefully discloses that results come back relevance-ranked rather than in a fixed order, which matters for interpreting output. It stops short of saying how many results come back or how ranking is determined.

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 sentence, front-loaded with the verb and resource, and the three examples directly disambiguate the expected query style. No 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?

For a two-parameter search tool with no output schema, the description covers the query intent but says nothing about the result shape (e.g. component objects with scores) or the limit semantics/default. Adequate but with clear gaps for an agent deciding how to call 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 description coverage is 0%, so the description must carry the load. It does explain the query parameter well ('a need described in words') with concrete examples, which is real added meaning over the bare string schema. The limit parameter (1-30) is left entirely unexplained, leaving a compensating gap.

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 specific verb ('Ranks') plus the resource ('components') and clarifies the input is a natural-language need, which distinguishes it from a plain enumeration like list_components. It does not name a sibling explicitly, so sibling differentiation is implied rather than stated.

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 examples ('switch between products', 'empty state') imply this is for fuzzy, intent-based lookup rather than exact IDs, and usage is inferable from the verb 'ranks'. However, there is no explicit when-to-use vs list_components/get_component guidance and no stated exclusions.

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