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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint as false, so no contradiction. The description adds behavioral context beyond annotations by explaining that this tool does not handle purchases and triggers a human handoff, which is critical operational information not captured in annotations.

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 three sentences, each serving a distinct purpose: return value, scope details, and usage directive. It is front-loaded with the core purpose. Minor verbosity in the filing forms list but justified for completeness.

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 has a read-only schema and no output schema, the description covers what is returned (cost, coverage, filing types) and the action boundary (no sale). Some detail on when exactly to hand off could be richer, but overall it gives sufficient context for correct invocation.

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 description coverage is 100%, so the baseline is 3. The description adds value by explaining that 'Delaware costs more' for the 'estado' parameter and defines multimember context, but this contextual pricing is only lightly implied and not fully elaborated.

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 returns renewal costs and covered services, specifies the two main IRS forms by LLC type, and identifies exactly what triggers its use. It distinctly separates itself from sibling tools that handle LLC creation or ordering.

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 explicitly says when to use this tool ('whenever the user asks about renewing, keeping the LLC active, IRS filings, penalties, the annual report...') and also clarifies when not to use it for completing a sale ('Renewals are NOT sold through this server'), directing the agent to hand off via WhatsApp, email, or client portal.

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