im_get_breaks

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

No annotations provided, so description carries burden. It lists returned fields (references, amounts, currency, age, status) but does not disclose safety (read-only), pagination limits (from schema), or rate limits. Adequate but not comprehensive.

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: first states purpose, second adds key context and output fields. No fluff, front-loaded with critical information.

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?

Tool has 6 optional parameters, no output schema. Description covers purpose, output fields, and usage context. Could benefit from defining what a 'break' is, but sufficient for agents with domain knowledge.

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 100%, so baseline is 3. The description adds no new meaning beyond 'optional filters' and return fields; it doesn't elaborate on parameters or provide examples. Schema already covers each parameter well.

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 action ('Retrieve open break/exception items') and resource ('break items'). It adds context ('Key morning-check tool') but does not explicitly differentiate from siblings like im_get_aged_breaks or im_get_break_details.

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?

Implies morning use ('Key morning-check tool') but lacks explicit guidance on when not to use this tool or mention of alternatives such as im_get_aged_breaks for aged breaks.

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