create_pa_breakdown

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

Annotations already declare readOnlyHint=false, idempotentHint=false, and destructiveHint=false. The description adds a meaningful permission requirement (`WRITE_ENABLED=true`) and clarifies the conceptual domain, which is more than the annotations alone provide. No contradiction detected.

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 sentences immediately state the operation, target table, prerequisite, and domain concept. Every phrase earns its place; no filler or redundancy.

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 covers purpose, prerequisite, and domain context, and the schema covers all parameters. There is no output schema, but for a create operation this is acceptable. It could mention return values or duplicate behavior, but that gap is partially covered by annotations.

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 already documents all four parameters with descriptions, examples, and defaults (100% coverage), so the baseline is 3. The description adds framing about how breakdowns are named and used but does not materially go beyond the schema's parameter details.

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 ('Create') with a specific resource ('PA breakdown' on `pa_breakdowns`), and clearly explains what a breakdown does semantically ('slice an indicator by a dimension'). This distinguishes it from sibling tools like `create_pa_indicator` and `list_pa_breakdowns`.

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?

It states a clear prerequisite (`WRITE_ENABLED=true`) and provides a concrete use case with examples ('Assignment group or Category'). It does not explicitly exclude alternatives or name sibling tools, but the context is sufficient for basic selection.

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