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

With no annotations, the description carries the full burden; it does disclose the shape of the result ('best matches with their pages') and a meaningful business constraint ('every engagement is quoted after the diagnostic'), telling the agent no pricing comes back. It omits that this is a read-only/non-mutating lookup and says nothing about limits or matching behavior.

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, front-loaded with purpose, then return shape, then the quoting caveat. Nothing is redundant, though the third sentence sits slightly apart from the invocation guidance.

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 one-parameter, no-output-schema recommendation tool, the description covers what it does, what comes back, and a key downstream expectation. The only gap is the missing sibling comparison, which matters because list_services is adjacent.

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% and the single 'need' parameter is documented as free text in the user's own words, so baseline is 3. The description goes beyond that by exemplifying the kinds of needs to pass in, which helps the agent compose a good value rather than a keyword.

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?

Specific verb+resource: 'Recommend the Blue Dot Brdg services that fit a business need,' with three concrete scenario examples that make the intent unambiguous. It does not, however, distinguish itself from the sibling list_services, so an agent must infer the difference.

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 scenario examples (foreign brand entering India, Indian brand exporting, founder wanting end-to-end brand management) imply when the tool applies, but there is no explicit 'use this instead of list_services' routing or any exclusion. Usage is inferred rather than stated.

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