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

Annotations already declare destructiveHint=true, idempotentHint=true and readOnlyHint=false, so safety is partly covered. The description usefully adds that it toggles the rental option on the widget and leaves the installed-fence catalog alone, which bounds the blast radius, but it never says whether a repeat call overwrites existing rental pricing or what the response is — the gap that matters most for a destructive mutation.

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 dense sentences, front-loaded with the audience and scope before the data requirements and the 'never invent numbers' rule. Every sentence carries information, though the parenthetical lists of periods and add-ons push length without adding much beyond the schema.

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 12-parameter nested-object mutation with no output schema, the definition covers audience, prerequisites, the widget side effect and the no-fabrication constraint. It is still missing overwrite/return semantics, which an agent would want before re-invoking a destructive 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 coverage is 75%, so the baseline is 3. The description maps its prose onto the domain fields (rate periods, minimum term, per-rental gate charges, delivery and setup fees, add-ons such as privacy screen and sandbag bases), adding light context, but it never mentions rental_only, panel_length_ft or setup_claim, leaving those to the schema alone.

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?

Names a specific verb and resource ('Set temporary fence RENTAL pricing') and immediately scopes the audience: rental companies for construction sites, events and security, not installers. It also states what the tool loads — products priced per linear foot per period plus gates, delivery, setup and add-ons — so an agent can distinguish it from the installed-fence pricing sibling without opening the 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?

Gives a clear condition for use (rental companies) and an implicit exclusion (installers; installed-fence catalogs are left untouched), plus the prerequisite that org_id and setup_claim come from create_contractor_account. It stops short of naming set_fence_pricing as the alternative for installers, which keeps it below the top mark.

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