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

Annotations already declare readOnlyHint=true and openWorldHint=false, and the description reinforces this correctly with 'Does not create a request: the homeowner enters their own details on the page.' It also adds the free-match and link-return context, which is beyond the structured fields, without contradicting them.

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 sentences that front-load the purpose before the parameter behavior and the non-mutation caveat. Efficient and readable, with only minor redundancy between 'what LocalHelpNow does' and 'how the match works.'

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 read-only, output-schema-less informational tool, the description covers what it returns (a link), what the params do, and the key boundary that no request is created. It could add whether authentication or an account is needed, but nothing essential for correct invocation 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%, so the baseline is 3, but the description adds real meaning beyond the schema: passing trade and area only prefills the request rather than executing a match, clarifying the parameters' effect. This is more than restating field definitions.

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 states a specific outcome: it explains the matching process and returns a link that starts a free match to one pro. It is distinguishable from find_pros (which presumably lists pros) by its 'how the match works + link' framing, though it never explicitly contrasts the two, so it falls short of a 5.

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?

Usage is only implied: 'Pass trade and area to prefill the request' tells the agent how to call it, and 'Does not create a request' clarifies a boundary, but there is no explicit statement of when to choose this over find_pros or the other siblings. Adequate but leaves routing to inference.

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