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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so safety is covered. The description adds behavioral context by specifying what the tool returns: a description of valid filters, groupings, metrics, detail fields, and citation fields. This goes beyond the annotations by outlining the tool's output content, but it does not mention potential nuances like whether the output is a schema or a textual summary. No contradiction with 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 a single sentence that is front-loaded with the action ('Describe') and the resource ('robotics.trade'), followed by a concise list of what is described. Every word earns its place; there is no redundancy or filler. This is an ideal level of conciseness.

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 description tool with no parameters and an output schema present, the description is complete. It enumerates all categories of information the tool provides (filters, groupings, metrics, detail fields, citation fields), which fully satisfies the need to understand what the tool outputs. The presence of an output schema means return values are already documented, so the description does not need to elaborate further. The tool is simple enough that no additional context is required.

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?

The tool has zero parameters, so the baseline score is 4 as per the rubric. The description does not need to explain parameter semantics because there are none. The empty input schema is consistent, and the description focuses on the output aspects rather than inputs, which is appropriate for a describe tool.

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 tool's purpose: 'Describe valid filters, groupings, metrics, detail fields, and citation fields for robotics.trade.' This is a specific verb ('Describe') with a clear resource ('robotics.trade') and enumerates the exact scope of the description. The title adds further context by specifying 'industrial-robot imports, value + robot counts', distinguishing it from sibling describe tools for other datasets.

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 provides clear context on when to use this tool: when one needs the valid filters, groupings, metrics, etc. for the robotics.trade dataset. It does not explicitly name alternatives or exclusions, but the resource-specific naming ('robotics.trade') and the presence of sibling describe tools for other datasets make the intended usage unambiguous. The lack of explicit 'instead of' language prevents a score of 5.

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