xero_create_tracking_option

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

No annotations are present, so the description must cover behavioral traits. It only mentions routing through an API under JWT/tenant scope but omits whether the operation is destructive, idempotent, or what side effects occur (e.g., creation of a record).

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 short but wastes space on routing details that may be implicit. It lacks focus on the actual operation. Could be more concise by omitting redundant routing info and adding operation-specific context.

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 complexity of creating a tracking option and the absence of annotations or output schema details, the description is severely incomplete. It does not explain the relationship to tracking categories, required data, or response format.

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?

With 0% schema coverage and no param descriptions, the description fails to add meaning. It only states 'arguments: JSON string of arguments' without specifying required fields, format, or examples. The agent cannot determine what to pass.

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 the tool is for creating a tracking option in Xero, which distinguishes it from siblings like `xero_create_tracking_category`. However, it does not explain what a tracking option is in Xero context.

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 provided on when to use this tool versus alternatives (e.g., `xero_update_tracking_options`). No prerequisites or context for invocation beyond routing info.

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