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

Annotations already establish read-only, idempotent, closed-world behavior. The description adds useful context beyond annotations: rules are public, dog stays require prior host approval, amounts are in EUR minor units, and fee amounts are not a live total quote.

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, both front-loaded and functional: the first defines the rule categories, and the second adds critical caveats about dog approval and EUR minor-unit amounts. There is no wasted text.

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 zero-parameter, read-only tool with rich annotations and no output schema, the description is nearly complete: it lists the rule categories and key caveats. It could be slightly stronger by stating the return shape or explicitly routing quote-related questions to get_quote.

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?

The tool has zero parameters and the schema is empty, so there are no parameter semantics for the description to compensate for. Baseline 4 applies for a no-parameter tool.

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 identifies the resource as public stay rules covering check-in, check-out, group, dog, cleaning, and event rules. It does not explicitly name a verb or distinguish this tool from siblings like get_dog_information or get_quote, but the resource scope is understandable.

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?

There is no explicit when-to-use guidance or named alternative. The caveat that amounts 'do not replace a live total quote' implicitly points agents to get_quote for pricing, but the description does not state when to choose this tool over get_dog_information or get_booking_options.

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