bexio Additional Addresses

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

Description discloses that delete is 'destructive, cannot be undone', which aligns with the destructiveHint annotation (true). It also specifies that create requires at least the name field. No contradictions with annotations.

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?

Description is a single coherent paragraph that front-loads the main purpose and uses semicolons to separate action details. It is concise and without filler, though formatting could be more structured with bullet points.

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?

Covers all actions, required parameters, and constraints (e.g., limit/offset for list, search fields). Lacks examples of payload or return values, but output schema is absent. Adequate for a multi-action CRUD tool.

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 covers all 8 parameters with descriptions (100% coverage). The description adds some context by summarizing actions and listing searchable fields, but does not significantly enhance understanding beyond the schema.

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?

Description clearly states it manages additional addresses of a contact, enumerates six specific actions with their required parameters, and differentiates from sibling tools (e.g., bexio_contacts) by focusing on a specific sub-resource.

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?

Description provides clear context by listing each action's prerequisites (e.g., contact_id required for all actions) and mentions searchable fields for the search action. However, it does not explicitly state when not to use this tool or suggest alternatives.

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