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

Annotations only declare the generic safety profile (readOnly=false, destructive=false, idempotent=false, openWorld=false). The description goes well beyond them: it discloses that an account snapshot (plan, platform, cadence, recent failures) is attached automatically, that replies arrive by email at the account address, that it works on a frozen site, and that throughput is capped at a few per hour.

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?

Roughly five short sentences, front-loaded with the action and payload before moving to prerequisites and rate limits. Every clause carries information, though the enumerated field list in the opening sentence partially duplicates the schema.

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?

With no output schema, the description closes the loop by explaining how the outcome is delivered (email reply to the account address) and what context the team receives automatically. For a 4-parameter submission tool this covers everything an agent needs to invoke it correctly.

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 all four parameters (site, subject, message, category) are already documented with length bounds and enum values. The description restates the parameter set and adds light guidance on what the message should contain, but contributes little syntax or format detail the schema does not already carry, so the baseline 3 applies.

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?

States a specific verb and resource ('Files a support request with the Blawgy team about this site') and enumerates the payload (subject, message, optional category). The scope is narrow enough to distinguish it from the many other sibling tools, and the mention of the account snapshot clarifies what the tool actually transmits.

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?

Gives explicit triggers ('when something is broken, when the help docs (search_help) cannot answer, or when the customer asks to talk to a person') and names the alternative sibling (search_help) with the condition that selects it. It also notes the frozen-site case, which is a meaningful branch condition.

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