athena_uncertainty_decompose

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

With no annotations, the description carries the transparency burden. It indicates a non-mutating read operation via 'Return' and adds 'Diagnostic only' as a behavioral constraint. However, it does not disclose potential side effects, prerequisites, or operational characteristics such as cost or model dependencies.

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, concise, front-loaded sentence that clearly states the action and output. 'Diagnostic only' adds a useful qualifier without unnecessary verbosity.

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?

The tool has seven parameters, no output schema, and no annotations, requiring the description to compensate. Although the description lists the output components, it omits all parameter guidance and usage context, making the description 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 provides no parameter semantics. None of the seven parameters (features, regime, arm_id, ridge, scope, ood_gain, target_coverage) are explained, leaving the agent without the information needed to construct a valid invocation.

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 returns a decomposition into specified uncertainty components and notes it is diagnostic only. It names the specific resource ('model-conditional proxy decomposition') and lists the components, but it does not explicitly differentiate from sibling tools like athena_uncertainty_calibrate.

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 phrase 'Diagnostic only' implies the intended use context but does not provide explicit when-to-use guidance or mention alternatives. No exclusions or alternative tool references are present, so the guidance is only implicit.

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