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

With no annotations provided, the description must fully disclose behavior, but it only says 'Inspect' which implies read-only without explicitly stating it. It does not clarify what the output looks like, whether any side effects occur, or how the request_id is used.

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 a single, front-loaded sentence with no fluff, but it is too terse to be truly helpful. It is concise but under-specified, sacrificing clarity for brevity.

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 no annotations and no output schema, the description must provide richer context about the domain ('normalized provider quotes', 'federated liquidity router') and the parameter's role. It does not explain what the tool returns or how the request_id connects to the quotes, leaving critical gaps.

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 coverage is 0% and the description never mentions the single parameter 'request_id'. The agent has no clue what this identifier refers to or how it should be formatted, making the parameter meaningless without additional context.

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 states a clear verb ('Inspect') and resource ('normalized provider quotes') within a specific context ('considered by the federated liquidity router'). It is distinct enough from many siblings, though it does not explicitly contrast with similar tools like me_get_supply_formation or me_get_supply_plan.

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?

No guidance is given on when to use this tool versus the many related sibling tools. The description does not mention any conditions, prerequisites, or alternatives, leaving the agent to guess.

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