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

While annotations confirm it is a read-only operation, the description provides essential behavioral context by stating 'results are suggestions to confirm with the person,' which prevents the AI agent from treating the output as definitive facts.

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 definition is perfectly sized and front-loaded. It is broken into two concise sentences where every word contributes to defining the scope or the behavior of 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?

The description effectively addresses the nature of the results, clarifying they are preliminary suggestions rather than final answers, which is the most important contextual information missing from the structured schema.

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?

Since schema description coverage is 100%, the baseline score is 3. The description adds minor value by specifying the input should be 'a plain description of the business' and defines what the mark represents.

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 the action (suggest) and the resource (classes, goods, and services wording), making it highly specific. This clearly differentiates it from siblings like 'list_classes' or 'get_application'.

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 usage is implied—use it when you have a plain description of the business. However, it does not explicitly guide when to use it over related tools or under what business conditions it should be invoked.

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