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

Annotations only cover the safety profile (non-destructive, idempotent write). The description adds genuinely useful context beyond them: submission triggers a human to read the entry and reply by email, i.e. an asynchronous, human-in-the-loop process rather than an instant programmatic response. It still does not state expected turnaround or whether the record is stored/visible anywhere.

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 definition leads with company positioning ("TrueRent helps companies get more value out of the way they already rent equipment... We don't tell you what to rent or who to rent from") that does not help an agent decide or invoke. The actual action and field list only appear in the second half, so the piece is not front-loaded around the agent's 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?

An output schema exists, so return values need not be explained, and the action plus collected fields are present. What is missing for a submission tool with three siblings is routing guidance and any statement of what happens after submission besides the email reply, leaving the agent to infer when this tool is the right choice.

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 the schema already explains all five parameters including the optional metro field. The description enumerates the four required fields but adds no format, validation, or routing meaning beyond what the schema states, 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?

The operative statement, "Ask a person at TrueRent to follow up," does convey a specific action and the description lists the collected fields (company name, contact name, email, what they rent). However, it is buried behind two sentences of marketing copy ("We don't tell you what to rent or who to rent from") that say nothing about the tool, and it never distinguishes itself from siblings like equipment_coordinator or how_truerent_works.

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?

"Confirm the details before calling" is a weak note about validating inputs, not guidance on when to choose this tool over equipment_coordinator or how_truerent_works. There is no explicit when-to-use, when-not-to-use, or alternative routing anywhere in the text.

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