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

With no annotations provided, the description carries the full transparency burden. It only says 'Query discarded,' hinting at no persistence, but does not disclose return format, errors, or side effects beyond discard.

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 very brief and front-loaded. Both sentences add value: the first states the core action, and the second clarifies that no query data is retained.

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 nine-parameter schema and no output schema, the description is incomplete. It does not clarify which parameter to use, what the return value looks like, or how this tool fits into the broader set of sibling tools.

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?

Although schema description coverage is 100%, the descriptions of the other eight parameters are irrelevant to counting search-query characters and are not reconciled with the tool's purpose. Only the 'query' parameter has meaningful semantics, but the rest create confusion.

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 the action ('Count characters') and the target ('a search query'), which matches the tool name. However, the schema includes many unrelated parameters, so some ambiguity remains about which input is actually used.

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 guidance is given about when to use this tool versus sibling tools. The description does not mention alternatives, prerequisites, or conditions that would help an agent select this tool.

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