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

With no annotations, the description must carry the full burden of behavioral disclosure. It mentions sorting order ('cheapest first') and a cost figure ($0.002), but does not state if the tool is read-only, whether it makes external calls, or any side effects. The behavior is not transparent enough for an agent to anticipate side effects or auth needs.

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 sentence with no fluff, placing the core function ('cost ladder') and the key sorting detail at the front. It is efficient, though brevity comes at the cost of missing critical information.

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 three parameters and zero schema coverage, the description is incomplete. It does not clarify parameter roles, usage context, or how it differs from cost-related siblings. Though an output schema exists, the lack of parameter explanation and usage guidance makes it insufficient for correct invocation.

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 0%, and the description does not explain any of the three parameters (text, calls, agent_id). The only hint is 'workload' which loosely maps to text, but no details on expected input formats, units, or how agent_id affects results. The description fails to compensate for the lack of schema documentation.

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 the tool provides a 'cost ladder for a workload across DDG routes' with sorting 'cheapest first', which clearly conveys that it returns cost comparisons. It does not explicitly differentiate from siblings like ddg_token_estimate or ddg_model_compare, but the purpose is specific enough that an agent can infer its function.

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 provided on when to use this tool versus alternatives such as ddg_token_estimate or ddg_run_paid_model. There is no mention of typical scenarios, prerequisites, or exclusions, leaving the agent to guess based on context.

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