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

With readOnlyHint=true and destructiveHint=false provided, the safety profile is already clear. The description adds valuable context: it evaluates against tenant protection laws and returns risk level, relevant state laws, and preventive recommendations – useful details beyond the annotations. No contradiction.

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?

Three sentences, each earning its place: purpose, evaluation method, and return values. Front-loaded with the core function, no fluff or repetitive content.

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?

No output schema exists, but the description lists return items (risk level, state laws, recommendations). It covers the main inputs and purpose. A minor gap is not explaining property_id's purpose and the slight inconsistency of mentioning state code when state is optional, but overall it is complete enough for a read-only analytical tool.

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 baseline is 3. The description's directive to 'Pass check_in_date, check_out_date, and state code' largely repeats schema info without adding formats or explaining property_id's role. It adds marginal value but is not misleading.

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 uses a specific verb and resource: 'Assess the risk of a guest establishing tenancy rights during an extended vacation rental stay.' This clearly distinguishes it from sibling risk-assessment tools like assess_vacation_rental_booking_risk, which cover broader booking risks.

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?

It provides clear context for use: extended vacation rental stays where tenancy rights may be a concern, and mentions evaluating stay duration against jurisdiction-specific laws. However, it does not explicitly name alternatives or state when not to use it, so it falls short of a 5.

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