word_count

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

No annotations exist, so description carries full burden. It fails to disclose definitions (e.g., what constitutes a word, sentence, paragraph), edge cases, or output structure. Vague behavioral traits reduce transparency.

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?

Two sentences with minimal waste. Front-loaded with key outputs. However, parameter description is redundant and could be removed. Structure is adequate but not optimized.

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 one parameter and no annotations, the description covers basic purpose but lacks behavioral details needed for a multi-output tool. Output schema exists but description doesn't mention it. Sibling list is large, so tool needs clearer distinction.

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 has one parameter 'text' with 0% description coverage. Description adds only 'Text to count words in,' which redundantly restates the schema's title. No additional semantics, constraints, or examples provided.

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 words, characters, sentences, paragraphs, and average word length. It uses specific verbs and resources, but does not differentiate from siblings like char_count or word_frequency, lacking explicit distinction.

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 on when to use this tool versus alternatives. The description only lists what it counts, omitting when-not-to-use or suggested contexts.

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