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

The description discloses that the query is discarded after the length check, providing some side-effect transparency. It doesn't describe what the tool returns or how it handles invalid or empty queries, and there are no annotations to fill this gap.

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 two short sentences with no filler. The core action is front-loaded and every word adds meaning.

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 tool's unusual nine-parameter schema and lack of an output schema, the description is incomplete: it doesn't explain the return format, the role of the other parameters, or typical use cases. It only covers the query parameter.

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 schema already fully documents the 'query' parameter as search text discarded after the length check, and the description adds little beyond restating 'search query'. The other eight parameters are not addressed in the description, but the schema descriptions cover them, so this is a baseline 3.

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 tool counts characters in a search query, giving a specific verb and object. It doesn't explicitly contrast with sibling tools, but the function is unambiguous.

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 intended use is implied: use it when you need the character length of a search query. There is no explicit statement of when to use it over alternatives or when not to use it.

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