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

Annotations already indicate readOnlyHint=false and destructiveHint=true. The description adds context about checklist completion and photo evidence, but does not explain what destructive behavior might occur (e.g., overwriting previous records) or any permission requirements. It adds some value beyond annotations but leaves notable gaps.

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?

Two sentences are concise and front-loaded. The first sentence states the core action and key features; the second gives usage context and parameter list. No wasted words.

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?

The description covers the tool's purpose, parameters, and user context well. However, it does not mention what the tool returns (no output schema) or explain the destructiveHint annotation's implications. Given the tool's moderate complexity, these omissions leave gaps.

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 100%, so the baseline is 3. The description adds value by explicitly listing parameters in prose, marking optional ones (checklist_items, issues_found, photo_urls, verified_by), and providing the allowed values for overall_condition. This clarifies usage beyond the raw schema.

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 action ('Record checkout verification') and the resource ('vacation rental'), with additional context about checklist and photo evidence. It differentiates from sibling tools implicitly since no other sibling handles checkout condition verification, though it does not explicitly name alternatives.

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 provides a clear use case: 'Used by cleaners or hosts to document property condition after a guest departure.' This tells when to use the tool, but it does not mention exclusions or alternative tools, so it misses the 'when-not' context.

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