xero_create_task

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

The description adds mechanism context beyond the annotations: the effect parameter is a claimed read/write that 'Spring verifies it', approval_ref is for 'resuming a write' (implying a write-approval workflow), and idempotency_key aligns with the idempotentHint annotation. However, the surprising destructiveHint=true is never reconciled — nothing explains what side effects or potential destruction the create carries. No contradiction with annotations is present.

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 Arg-list format is clean and each parameter gets exactly one short line, which is parseable. But the first sentence duplicates the tool name, and some lines are near-tautological ('Exact project correlation reference'). The space saved by brevity is not reinvested in domain semantics, so the structure is adequate rather than excellent.

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 7-parameter wrapper with 0% schema coverage, the description is incomplete: it explains routing and approval mechanics but never the domain operation, the shape of the `arguments` payload, or when approval_ref becomes necessary. The output schema covers return values, yet an agent still cannot construct a correct invocation of the Xero task creation, and the destructive hint remains unexplained.

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 0%, so the description carries the full burden, and it does assign a one-line role to each of the 7 parameters. But the most important field, `arguments`, is circular — 'JSON string of arguments for the connector operation' — leaving the actual Xero task payload undefined. With all parameters optional (required=0), the description also never clarifies which of project_id, project_ref, or connector_account_ref are actually needed for a valid call.

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 opening sentence merely restates the tool identity — 'Xero connector operation create_task (platform tool xero.create_task)' — which is a near-tautology that adds no domain semantics. The only substantive sentence concerns governance routing ('Routes only through the exact project/account governed connector authority'), not what the operation accomplishes. An agent cannot tell what a Xero task is, what creating one entails, or how this differs from siblings like xero_create_invoice or create_crm_task.

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?

There is no guidance on when to use this tool versus alternatives, no named exclusions, and no use-case context. Sibling tools include salesforce_create_task, clio_create_task, smokeball_create_task, and create_crm_task, but nothing helps an agent choose among them. The routing constraint describes a platform-level requirement, not a selection criterion.

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