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

Annotations already cover read-only and open-world behavior, and the description adds meaningful context beyond that: the inventory is live and currently available, results include grading report numbers and product URLs, and MCP-capable hosts render an interactive card grid. This is useful behavioral detail without contradicting the annotations.

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 is compact and front-loaded, leading with the core search action and then providing return-value and usage context. Each sentence contributes useful information, though the final MCP Apps sentence is somewhat tangential for an agent deciding whether to invoke the tool.

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 10-parameter, all-optional search tool with a rich schema, a detailed output schema, and safety-bearing annotations, the description is sufficiently complete. It covers purpose, return contents, and a clear use case. It could be slightly stronger by noting that all filters are optional and that a broad unfiltered search is possible, but the schema already conveys that.

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 schema already explains all 10 parameters. The description reinforces that search can be by shape, carat weight, price, color, clarity, and cut, which maps to the parameters, and hints at budget as a use case. However, it does not add material meaning beyond the well-documented schema.

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 states a specific verb and resource: searching Ada Diamonds' live loose lab grown diamond inventory, with the search dimensions enumerated. It also specifies that results include grading report numbers and product URLs. It does not explicitly contrast itself with sibling tools like search_engagement_rings or search_jewelry, but the 'loose lab grown diamond' scope makes the boundary reasonably clear.

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 gives a clear trigger: 'Use this for any question about what diamond a budget can buy.' This provides actionable context for when to select this tool. It does not explicitly state when not to use it or name alternative sibling tools, so it stops short of a 5.

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