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

Annotations already declare readOnlyHint=false, destructiveHint=true, idempotentHint=false, and openWorldHint=true, so the safety profile is covered. The description adds genuinely new behavioral context: the record is created unpriced with no payment requirement, and the call requires authentication plus an Aisle membership. It does not explain duplicate-name handling, which would have pushed it to a 5.

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?

Four short sentences with the core action and required inputs front-loaded and no filler. Slightly list-like, but every sentence carries information an agent needs.

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 an 11-parameter mutation tool with no output schema and annotations covering the safety profile, the description covers required inputs, auth/membership gating, and the unpriced nature of the created room. Only edge behavior (duplicates, multi-wedding selection) is left to the schema, which is acceptable.

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% across all 11 parameters, so the schema already documents names, dates, capacity, and the multi-wedding condition on wedding_id. The description only restates that property_name and room_name are required and adds the no-payment attribute, so the baseline 3 applies.

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 ('Adds an unpriced room under a named property in the selected wedding'), and the qualifier 'unpriced' distinguishes it from pricing-related siblings. It is clearly separable from add_my_event, add_my_guest, and update_my_accommodation without opening any schema.

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 supplies prerequisites (sign-in, Aisle membership, required property and room names) but never states when to use this versus update_my_accommodation or list_my_accommodations. Usage is implied by the prerequisites rather than explicitly framed as when/when-not.

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