Sales_getOrderMetrics

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It implies a read-only operation by saying 'Returns aggregated order metrics,' but it does not clarify authentication needs, rate limits, side effects, output structure, or what 'not here' means operationally.

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 briefly worded, which is good, but the opening 'Catalog entry' sentence is meta and adds little value. The purpose sentence is front-loaded enough, but the overall structure could be tighter and more informative in the same space.

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?

With no input schema details, no annotations, and no output schema, the description must do more heavy lifting. It leaves an agent without enough context to invoke the tool correctly, omitting required parameters, input format, and response shape.

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 input schema is empty but allows additional properties, so the description's mention of interval, granularity, and buyer type adds some meaning. However, it does not provide actual parameter names, formats, allowed values, required fields, or mention likely critical inputs like marketplace IDs.

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 uses a specific verb and resource ('Returns aggregated order metrics') and identifies key dimensions (interval, granularity, buyer type). The opening 'Catalog entry' phrase is tangential, but the core purpose is still clear enough to distinguish this from most siblings.

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?

There is no guidance on when to use this tool versus alternatives, no exclusions, and no mention of related tools. The only additional context, 'Runs in your Kuudo deployment, not here,' is about execution environment, not usage decision-making.

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