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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint, and destructiveHint=false, so the safety profile is covered. The description adds useful behavioral context by saying the tool is 'free, advisory and non-executing,' but it does not explain outputs, latency, rate limits, or how constraints affect 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?

The description is two short sentences with no wasted text, front-loading the compatibility-alias relationship and then adding behavioral qualifiers. It is appropriately sized for what it chooses to say.

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 tool with a nested constraints object, no output schema, and open-world behavior, this description is far too thin. It establishes that the tool is a non-executing alias but leaves out what the agent gets back, how the alias differs operationally, and how constraints shape 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 only 50%, and the description itself says nothing about either parameter. The task parameter is documented in the schema, but the large nested constraints object is undocumented in both the schema and the description, leaving an agent without guidance on how to use it.

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 identifies the tool only as a compatibility alias for find_or_quote_task, so its purpose is inferred from the name/title and sibling rather than stated directly. It does distinguish the tool from non-alias siblings by making clear it is a compatibility path, but it does not explain what 'find best service' actually returns or does.

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 phrase 'Compatibility alias for find_or_quote_task' hints at when it might be used, but there is no explicit guidance on when to choose this tool versus find_or_quote_task or the other siblings. 'Free, advisory and non-executing' clarifies constraints but not selection criteria.

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