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

Annotations already declare readOnly/idempotent/openWorld/no-destruct, so the safety bar is covered. The description adds genuine value beyond that: no auth requirement, empty-results semantics with an explicit anti-hallucination instruction, a caveat that results are not quality certification or payment proof, and a version/digest pinning step before reuse. Return format and pagination remain unstated.

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?

Purpose is front-loaded in the first clause, and each following sentence carries a distinct constraint (auth, empty results, data caveats, version pinning). The caveat sentence is the longest and slightly dense, but nothing is filler.

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 search tool with no output schema and zero schema-level parameter docs, the description covers the important agent questions: credentials, empty results, trust level of results, and reuse safety. The notable remaining gap is what the returned items actually contain and whether results are paginated.

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 0% and the single parameter is a nested object with q and industry fields. The description compensates partially by giving example query values ('automation, customer support or software') that map to q, but the industry field and the q/industry split are never explained.

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?

States a specific verb and resource: 'Find public delivery acceptance templates'. The search-by-scenario framing implicitly separates it from the getPublicSpecification sibling, which fetches by identity, but the description never names that alternative. Clear but not explicitly differentiated from siblings.

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?

Gives real context for when to call it ('before asking a user to connect') and a precondition ('No credential needed'), plus handling for the empty-result case. It stops short of naming getPublicSpecification as the follow-up tool once a template is chosen, so the routing is only implied.

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