Replenishment20221107_getSellingPartnerMetrics

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

With no annotations, the description carries the full burden. It does disclose that the tool executes in a Kuudo deployment rather than the current environment and indicates a read-style behavior ('Returns...'). However, it does not clarify permissions, whether the operation is fully read-only, what happens when called, or what the returned metrics actually contain.

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 brief and mostly front-loaded, with no filler. The phrase 'Catalog entry' and 'Runs in your Kuudo deployment, not here' are slightly redundant as deployment-oriented caveats, but overall the description remains efficient and readable.

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 simple zero-parameter read tool, the description is nearly adequate, but it leaves ambiguity about whether the tool is actually callable from this environment. Since there is no output schema, the vague phrase 'aggregated replenishment program metrics' provides limited detail about what values the agent should expect.

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 has zero parameters, so the description does not need to explain parameter usage. The baseline for zero-parameter tools is strong, and the description adds no misleading parameter information.

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 identifies the operation as returning 'aggregated replenishment program metrics for a selling partner,' giving a specific verb and resource. It also adds deployment context ('Runs in your Kuudo deployment, not here') that helps distinguish this from tools in other domains, though it does not explicitly compare it to similar metrics tools.

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 about when to use this tool versus alternatives. The statement 'Runs in your Kuudo deployment, not here' is a deployment caveat, not a usage guideline, and no alternative tools are suggested. An agent is left to infer whether and how it should invoke this tool.

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