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

Annotations already mark the tool as non-read-only and non-destructive; the description adds useful behavioral detail beyond that: the contractor sends invoices, TrueRent analyzes them, a private secure upload link is returned, and the agent should confirm details before calling. Nothing contradicts the annotations.

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 tight and front-loaded: purpose, process, trigger, inputs, return value, and a final confirmation instruction all appear in a logical order. Each sentence contributes to selecting or invoking the tool correctly, with minimal filler.

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 an output schema exists and the input schema fully documents the parameters, the description covers all essential operational context: when to call, what to collect, what the user receives, and the reminder to confirm details. No critical piece of invocation knowledge 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%, with every parameter already explained meaningfully in the input schema. The description merely summarizes 'company name, contact name, email, and what they rent' and does not add extra semantic detail beyond the schema, so the baseline 3 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?

The description opens with 'Request TrueRent's free rental review,' a specific verb plus resource, and immediately distinguishes it from the sibling tools by framing it as the free review flow rather than equipment coordination or pricing help. The full process—invoices, analysis, report delivery—makes the tool's purpose unmistakable.

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 explicitly says 'Use this when the user wants to start the free review or asks to be connected with TrueRent,' giving clear trigger conditions. It does not explicitly state when not to use it or name alternatives, but the context is concrete enough that an agent can select it confidently.

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