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

With no annotations provided, the description carries the full burden of disclosing behavior. It reveals key traits: no consent collection needed, authentication effects (signed link and 20% credit), and constant homeowner pricing. It also flags the 'fictional sample' aspect of the shareText. This is comprehensive for a tool returning a URL and text.

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 packs extensive information into a focused paragraph. It front-loads the main purpose and then adds behavioral details. The use of '[always free — no API key required]' is a helpful at-a-glance summary. While slightly dense, every sentence adds value.

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 0 required parameters, no output schema, and no annotations, the description does a good job of explaining the return structure (url, shareText, quoteGuardian object) and usage flows. However, it omits details about the format of the returned URL and does not specify error cases or fallback behaviors, which would improve completeness.

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 100%, so the schema already describes zipCode, country, and contractorCategory well. The description adds minimal parameter meaning beyond the schema—it mentions zipCode implicitly for free assessment and contractorCategory pre-selection, but does not explain defaults or edge cases. 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 clearly uses verbs like 'convert', 'Returns', and 'paste' to indicate the tool generates a URL and share text for two distinct use cases: a free assessment or a Quote Guardian object for existing proposals. This distinguishes it from siblings like 'get_builder_upgrade_link' or 'create_energy_assessment', though differentiation from 'get_builder_upgrade_link' could be sharper.

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 provides explicit guidance: use the shareText for free assessment generally, or the quoteGuardian.shareText for homeowners with an existing proposal. It also states when not to use it ('No consent collection is required from you; use route_lead only when explicit consent is already captured'). This is strong but lacks explicit comparison to sibling tools like 'get_builder_upgrade_link'.

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