search_calendar_years

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

The description implies a read-only operation ('Search'), but annotations set readOnlyHint=false, indicating potential state modification. This is a direct contradiction. Additionally, no side effects, auth needs, or other behavioral details are disclosed beyond what annotations already provide.

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 one sentence but conveys no information beyond the tool name. It is under-specified rather than concise, as every word is redundant and no value is added.

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 a required 'body' parameter that is completely opaque ('as defined by the bexio API'), no output schema, and no explanation of what searching calendar years entails, how results are returned, or how it differs from listing. The description is wholly inadequate for an agent to use this tool correctly.

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% for all three parameters (body, limit, offset), so the schema carries this burden. The description adds nothing about parameters, which is acceptable given the baseline, but it also does not clarify the opaque 'body' parameter beyond the generic API reference.

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 'Search calendar years' is a verbatim restatement of the tool name, offering no additional detail or differentiation from sibling tools like 'list_calendar_years' or 'get_calendar_year'. It identifies a verb and resource but is essentially tautological.

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 description gives no guidance on when to use this tool instead of alternatives. It does not mention search criteria, relationship to list/get operations, or any context in which this tool is preferred.

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