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

Annotations already declare readOnly, openWorld, idempotent, and non-destructive behavior. The description adds value beyond annotations by revealing that the tool returns all policy facts in a single call and that amendment rules are conditional ('when configured'), which is useful behavioral context.

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 efficient sentences, with the core scope and concrete policy facts front-loaded before the usage instruction. Every clause earns its place and there is no redundant repetition of the title or annotations.

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 tool has only one parameter, full schema coverage, helpful annotations, and an output schema, so the description does not need to explain return values. The description provides the scope, the exact policy facts, and a clear usage rule, making it complete for agent 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 coverage is 100% for the single listing parameter, including the note that partial titles are acceptable. The description reinforces the parameter's role by saying 'ONE listing' but adds no meaning beyond what the input schema already provides, so the baseline score of 3 is appropriate.

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 states a specific action and result: retrieving every policy fact for one listing, then enumerates the concrete facts (check-in/out times, advance notice, cancellation policy). The 'ONE listing' scoping clearly distinguishes it from broader listing or availability tools.

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 gives an explicit usage rule: 'Use for ANY rules/policy question about a home.' This is clear and actionable, though it does not name sibling alternatives or state when not to use the tool; the rule alone is sufficient for most agent routing.

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