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

With no annotations, the description carries the full burden for behavioral disclosure. It explicitly states the metrics returned, which is transparent, but it does not explain how 'estimated tokens' are estimated or what formula/scales are used for 'readability grade'. It also doesn't mention any side effects, though the tool appears read-only.

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 a single, front-loaded sentence that lists the key metrics. It is succinct and avoids unnecessary filler, every word earning its place.

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 simple, and the description covers the core purpose, but because there is no output schema, the return format is undefined. The description lists metrics but doesn't specify the structure (e.g., JSON object keys, value types) or clarify the nature of 'estimated tokens' and 'readability grade', which are common sources of ambiguity.

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 has a single 'text' parameter with 0% coverage, so the description must compensate. The description adds meaning by indicating that the input should be text with sentences and words, which is inferred from the mentioned metrics like sentence count. However, it doesn't specify format constraints (e.g., plain text vs markdown) or maximum length.

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 ('Get') and the resource ('text quality metrics'), then lists specific metric types: word count, sentence count, estimated tokens, readability grade. This distinguishes it from sibling tools like compare_responses and score_response, which focus on comparison and scoring.

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 description implies usage when text metrics are needed but provides no explicit guidance on when to use this tool versus compare_responses or score_response. No exclusions or alternatives are mentioned, leaving the agent to infer the appropriate context.

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