bexio Notes

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

The description goes beyond annotations by detailing the permanence of delete ('cannot be undone') and noting that search returns results based on criteria. Annotations already indicate destructiveHint=true, readOnlyHint=false, and idempotentHint=false. No contradictions exist.

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 front-loaded with the overall purpose and action list. Each sentence adds necessary detail. It could be slightly tighter but remains well-structured and informative without 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?

Given no output schema, the description covers all actions and their parameter requirements. It explains pagination (limit/offset) and search criteria structure. It could mention return format, but the action names imply expected outputs (list returns array, get returns object).

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%, baseline 3. The description adds value by grouping required fields per action (e.g., 'Required on create: user_id, event_start, subject') and listing searchable fields for the search action. This provides meaning beyond the schema's individual field descriptions.

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 it manages notes in bexio and enumerates six specific actions (list, search, get, create, update, delete). It distinguishes notes as 'short annotations linked to a user and optionally a contact, project or module entry', which differentiates it from other bexio entity tools.

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 provides explicit parameter requirements per action (e.g., 'id required for get/update/delete', 'payload required on create: user_id, event_start, subject'). It warns that delete is permanent. While it doesn't explicitly exclude alternatives, the action list and sibling tool names provide sufficient context.

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