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

Goes well beyond the annotations: discloses a hard rate limit (10/account/UTC day), the human nature of replies, retry semantics via idempotency_key, and a required support:write scope that is off by default and owner-granted. This is exactly the operational context an agent needs before calling a write tool.

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?

Four short sentences, each carrying a distinct operational fact (purpose, rate limit, idempotency, auth). The most important constraints are front-loaded and nothing is padded.

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 write tool with no output schema, the description covers purpose, quota, retry safety, and permission prerequisites. An agent has everything needed to decide whether it can even call this tool and how to retry it safely.

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 coverage is 33%; only idempotency_key is documented in the schema, and the description usefully reinforces its retry use. But title and message semantics (length caps, content expectations) are left entirely to the schema with no added meaning.

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 ('Open a ticket with human support') and disambiguates the audience ('replies come from staff, not from an AI'). It does not, however, distinguish itself from the sibling everyinfra_create_ticket, which the agent must tell apart.

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 'human support' framing and the daily cap imply when this channel is appropriate, but the description never names the alternative (e.g. everyinfra_create_ticket or everyinfra_chat) or states when not to use it. Use context is implied rather than explicit.

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