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

No annotations are provided, so the description carries the full burden. It discloses that the tool scores, rates, suggests, and rewrites, and also mentions the cost per call ($0.10) and payment method. This provides a clear behavioral picture, though it does not explicitly state any side effects or limitations.

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 packed with useful information and is well-structured, starting with the main purpose. It is slightly longer than minimal but every sentence adds value. It could be trimmed slightly without losing meaning, but overall it is effective.

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 no output schema, the description explicitly details what the output contains: a multi-criteria scorecard, rating, top suggestions, and an improved rewrite. All parameters are covered, and the description addresses the tool's complexity fully, making it ready for agent use.

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 input schema has 100% description coverage for the three parameters. The description adds context by specifying the types of text (email, social post, customer reply) and the optional goal and format parameters, which goes beyond the schema's brief descriptions. This adds meaningful value for agent selection.

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's purpose: reviewing and improving agent outbound text before sending. It lists specific criteria (clarity, spam-safety, tone, etc.) and outcomes (scorecard, rating, suggestions, rewrite). This specificity distinguishes it from sibling tools such as agent_content_scan or agent_analysis_report, which likely have different scopes.

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 for any outbound text from an agent (email, social post, customer reply) and is clear about the context. However, it does not explicitly state when not to use this tool or compare it to alternative tools, leaving room for ambiguity.

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