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

Annotations already declare destructiveHint=true and readOnlyHint=false, so the agent knows this is a mutation. The description adds the primary/backup role concept and scheduled_date context, which is useful. However, it does not disclose whether assigning a cleaner overwrites an existing assignment or any constraints on backup assignments, leaving some behavioral ambiguity.

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?

The description is two sentences, front-loaded with the core action and immediately followed by a concise parameter guidance list. Every word earns its place, with no fluff or repetition.

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?

Given that the schema fully documents parameters and there is no output schema, the description is mostly complete: it states the action, the timing, role options, and required vs optional inputs. It would benefit from mentioning whether existing assignments are replaced, but the destructive annotation already signals mutation, so this is a minor gap.

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 input schema already provides 100% coverage with descriptions for all five parameters. The description only restates the parameter names and highlights that role is primary/backup and scheduled_date is optional, which is redundant with the schema. The only slight addition is the phrase 'between bookings' contextualizing scheduled_date, but overall it does not add significant semantic value beyond the 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 a specific action ('Assign a cleaner') and the target resource ('vacation rental property turnover between bookings'). This verb-object structure distinguishes it from sibling tools like get_rental_cleaning_schedule or create_rental_maintenance_task, making its purpose unambiguous.

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 clear usage context: it is for assigning cleaners to turnovers between bookings. It does not explicitly mention when to use alternatives like get_rental_cleaning_schedule for viewing assignments, but the context is sufficient to infer the intended use. A brief exclusion note would have earned a 5.

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