bexio Tasks

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

Annotations indicate destructiveHint=true, and the description confirms that delete is permanent and cannot be undone. It also details that create requires specific fields. No additional behavioral traits beyond what annotations already provide are disclosed, but the description does not contradict 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?

The description is fairly concise given the complexity of eight actions and many parameters. It front-loads the general purpose and then details each action. Some redundancy exists (e.g., repeating 'order_by' for different actions), but overall it's well-structured and efficient.

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 multi-action tool with no output schema, the description is complete. It covers all eight actions, their required/optional parameters, and cross-references to other tools (list_statuses, list_priorities). The agent can correctly select and invoke the tool based on this description.

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%, so baseline is 3. The description adds some context, e.g., for search it lists searchable fields, and for create it notes required payload fields. However, it does not elaborate on parameters like info, place, or sub_contact_id beyond what the schema already describes.

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 tasks/todos in bexio and enumerates eight specific actions (list, search, get, create, update, delete, list_priorities, list_statuses). It distinguishes itself from sibling tools like bexio_contacts or bexio_projects by focusing on task management.

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 detailed guidance per action: for search, it specifies search_criteria required; for create, it lists required fields (user_id, subject) and references list_statuses/list_priorities for status/priority IDs. It also explains order_by options. However, it doesn't explicitly state when to avoid certain actions or when to use alternatives.

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