m3_cost_centers

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

With no annotations provided, the description carries full responsibility for behavioral disclosure. The 'Read/write' claim is vague and misleading given that the schema only permits skip/take pagination parameters and has no mutation-related inputs. It does not state side effects, permissions, pagination behavior, or output structure.

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 very short, but the phrases 'controlling variable' and 'Read/write' add noise rather than value. The core query statement is buried among ambiguous fragments and does not earn its place.

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 paginated query tool with no output schema or annotations, the description should at least clarify that this is a read-only listing operation and how pagination works. It does not, and the 'Read/write' fragment actively undermines the otherwise simple query intent.

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 does not mention the skip/take parameters, their defaults, or their limits. The tool description adds no semantic context for how pagination works or what results the agent should expect.

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 'Query cost centers (střediska)', giving a specific verb and resource. However, the trailing 'Read/write' creates ambiguity about whether this tool also performs mutations, and the 'controlling variable' phrase does not clarify the purpose further.

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 like m3_create_cost_center. The description provides no context about prerequisites, filtering, or situations where another sibling would be more appropriate.

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