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

The annotations already declare readOnlyHint=true and destructiveHint=false. The description adds useful behavioral context: the tool only generates a pre-filled link, the homeowner submits it themselves, and no direct project creation occurs on the agent's side. This clarifies the read-only nature beyond 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 compact and front-loaded with the core action, then adds a clear usage directive. It is slightly dense but each sentence earns its place and no extraneous content appears.

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 tool with no output schema, the description still makes the return value implicit ('give them this link') and covers the complete user flow. It also includes the use trigger and explains why the tool exists, which is sufficient given the schema's full parameter coverage.

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 input schema already documents all six parameters well. The description adds no additional parameter-level detail, but does not need to—the schema carries the full burden and the baseline of 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 description clearly states the specific action ('Build a personalized link') and the resource ('The Renovation Room's free project-submission form'). It also conveys the intended outcome—homeowner reviews and submits, contractors are alerted—which distinguishes it from sibling tools like search_pros or renovation_faq.

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 includes an explicit trigger: 'Use after the user describes a real project they want quotes for.' It provides clear context for when the tool is appropriate, though it does not explicitly list when not to use it or name alternative tools.

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