create_pa_breakdown

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

The description adds the permission requirement beyond annotations, and explains the conceptual behavior. Annotations already indicate non-readonly and non-destructive, so no contradiction. Could mention side effects or error states.

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?

Two concise sentences that efficiently convey action, prerequisite, and purpose. No wasted words.

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 description lacks information about the return value or outcome, and does not mention validation or error scenarios. Without an output schema, this is a gap. However, annotations and schema cover many aspects adequately for a create tool.

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 coverage is 100% and each parameter has a description. The description provides high-level context but does not add significant per-parameter meaning beyond the schema. Baseline score of 3 is appropriate.

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 creates a PA breakdown, specifies the target table, and explains what breakdowns do (slice an indicator by dimension). This distinguishes it from other create_ tools like create_pa_indicator.

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?

Includes a prerequisite (WRITE_ENABLED=true) and an example of slicing by dimension. However, it does not explicitly state when to use this tool versus alternatives like update_pa_breakdown or list_pa_breakdowns.

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