xero_create_task

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

With no annotations, the description must fully disclose behavioral traits. It specifies that the tool routes through an API but does not mention side effects (e.g., whether creation is idempotent, what happens on duplicate, or required permissions). The behavior of the 'create_task' operation is essentially opaque, providing minimal assurance beyond it being a connector operation.

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 concise with only two sentences and an 'Args' line, which is not overly verbose. However, the first sentence redundantly states the tool name and platform tool. The structure is acceptable but could front-load more useful information, such as the purpose of the task in Xero, rather than routing details.

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 the tool's simplicity (one parameter, no output schema shown despite having one), the description should provide a complete picture. It fails to mention the output or return value, which is important for understanding the result of a creation action. The routing information is of secondary importance, and critical context about task creation is missing.

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?

The schema has 0% coverage, so the description must explain the 'arguments' parameter. It merely states it is a 'JSON string of arguments for the connector operation,' which adds little meaning. The agent has no guidance on the structure or required fields within the JSON, making parameter usage uncertain.

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 states it is a 'create_task' operation for Xero, which indicates the verb (create) and resource (task). However, it lacks specificity about what a task is in Xero's context, making it hard to distinguish from other create tools like xero_create_invoice or xero_create_contact. The platform tool name is provided, but without domain-specific details, the purpose remains somewhat vague.

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?

No guidance is provided on when to use this tool versus alternatives (e.g., other create tools or xero_list_tasks). There is no mention of prerequisites, constraints, or typical use cases. The description only explains routing, leaving the agent without context for appropriate invocation.

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