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

No annotations are supplied, so the description carries the full burden of behavioral disclosure, and it discloses nothing. There is no statement about read-only nature, result scope, ranking, or limits, even though a search tool's behavior (does it return snippets? full docs? how many hits?) matters for correct invocation.

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?

It is short, but brevity here comes from omission rather than efficiency. The single sentence is a name-and-alias echo that contributes no information, which is under-specification rather than genuine conciseness.

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?

The tool is structurally simple (one required string, no output schema), so the bar is low, but the description still fails it: no platform-vs-shared routing, no note on what is searched or returned. Against zero annotations it does not supply enough for confident invocation.

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 100% and the lone 'query' parameter is documented in the schema as 'Search terms for bundled SDK references.' The description adds no syntax, phrasing, or scoping advice beyond that, so the baseline 3 for a fully schema-documented parameter set 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 only restates the tool name and adds a parenthetical alias '(reference-search)'. It never states in prose that this searches SDK reference documentation, nor does it distinguish kotlin:: from the ~10 sibling api.reference.search variants for other platforms. This is essentially a tautology of the identifier.

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 when-to-use guidance is provided. With parallel siblings like shared::api.reference.search and android::api.reference.search, an agent receives no signal about when Kotlin-specific lookup is preferable to the shared variant. Use is only weakly implied by the platform prefix in the name.

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