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

Annotations declare the safety profile (readOnly/idempotent/non-destructive), and the description adds genuinely new behavior: missing, removed and other-wedding rooms all collapse to the same not-found result, guest assignments and occupant identities are excluded, and sign-in is required. That is exactly the kind of edge-case and auth disclosure annotations cannot carry.

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?

Front-loaded with the return payload, then edge-case behavior, exclusions, and auth in three efficient sentences. The field enumeration is slightly dense but justified given there is no output schema to carry it.

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 no output schema, the description takes on the burden of describing the returned shape and does so thoroughly, while also covering not-found semantics, exclusion rules, and authentication. Nothing essential for correct invocation is missing.

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 description coverage is 100%, so both parameters are already documented by the schema. The description reinforces that the room belongs to a 'selected wedding' but adds no format or syntax detail beyond that, so the baseline 3 for a fully-covered schema 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?

States a specific verb and resource: 'Returns one identified room in the selected wedding', immediately distinguishable from the sibling list_my_accommodations. It also enumerates the returned fields (property, capacity, status, stay details, overrides), so an agent knows exactly what this singular getter yields.

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 singular 'one identified room' framing implies this is the by-id lookup counterpart to list_my_accommodations, but the description never names the alternative or states the condition for choosing it. The scoping note about other-wedding rooms is behavioral context rather than usage guidance.

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