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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and closed-world, so the safety profile is covered. The description adds genuine behavioral context beyond that: the check is rule-based, not an LLM, and lightweight, which sets expectations about determinism and the limited scope of detected issues. It stops short of describing the response shape or how issues are reported.

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?

A single front-loaded sentence that states purpose first, then the mechanism caveat, then the detected issue types. The 'client and server side from freedailypro' branding is the only filler, but otherwise every clause earns 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?

For a simple one-parameter tool with no output schema, the description covers what the tool does and how it works, which is largely sufficient. However, with no output schema present the description should at least sketch what a result looks like (e.g., a list of flagged issues with positions), and it does not.

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?

There is one required parameter ('text') with 0% schema description coverage, so the schema itself says nothing about it. The description implies text is the input to be checked but gives no syntax, size limit (maxLength 20000), or formatting guidance, leaving the schema to carry only the type constraint.

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 names a specific verb+resource (grammar checking of supplied text) and enumerates the exact error classes detected (misspellings, spacing, capitalization, repeated words). It partially differentiates from siblings by clarifying it is rule-based rather than an LLM, which separates it from tools like paraphrase_text, but it never names an alternative directly.

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?

Usage is only implied: an agent can infer it should call this when it wants mechanical proofreading of a passage. There is no explicit 'use this when / prefer X instead' guidance against near neighbors such as analyze_readability, word_count, diff_text, or find_and_replace.

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