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

Discloses access requirement (host) beyond annotations. Annotations are minimal (no readOnly, destructive, etc.), so description adds some value but does not describe side effects or data impact.

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?

Single sentence covering purpose and key constraints. Front-loaded with action and scope. Slightly dense but concise; no redundant content.

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 20 parameters, no output schema, and minimal annotations, the description omits many parameter details, return behavior, and additional constraints beyond host requirement. Incomplete relative to tool complexity.

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?

With 0% schema description coverage, description lists a few fields (category, status, etc.) but does not explain most of the 20 parameters. Agent must infer meaning from names and enum lists, which may be insufficient.

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?

Explicitly states it adds a physical asset/gear item to a live event's inventory. Names key fields and requirements. Unique among sibling tools, no ambiguity.

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?

Clearly states required parameters (event_id + name) and access condition (must be a host). Provides context for when to use, though does not explicitly contrast with alternatives.

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