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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds useful cost context about Parser credits, which annotations cannot express, but says nothing about result format, ranking, or result limits — notable for a discovery tool.

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?

It is a single short sentence, so nothing is bloated, but the credit-policy clause leads without context and reads as a non sequitur for an agent that has not yet seen the tool list. The core purpose is dispatched in four words while the remainder is spent on billing minutiae.

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?

With no output schema and no annotations describing returns, the description is the only source for what this tool produces, and it omits that entirely. For a discovery tool whose whole value is the returned catalog, this is a substantial gap that leaves the agent guessing how to consume results.

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% and both parameters (query, toolset with its enum) are documented in the schema, so the baseline of 3 applies. The description adds no syntax hints for query phrasing or guidance on which toolset value maps to which task family.

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?

"Find tools/workflows" states a specific verb and resource, and the title reinforces it as task-based tool discovery. No sibling tool performs discovery, so no differentiation is needed, though the description never explains what a result looks like (tool names, descriptions, workflows).

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?

There is no explicit statement of when to call this versus invoking a sibling tool directly, nor whether it should be used before multi-step CLM operations. The credit note ("CLM contracts use no Parser credits; separate Parser bulk processing uses Parser credits") implies a routing consideration for the toolset choice but leaves the actual selection rule implicit.

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