xero_delete_feed_connection

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

No annotations provided. Description lacks behavioral details such as destructiveness, authentication requirements, or side effects. For a delete operation, one would expect a warning about irreversibility or required permissions, but none are given.

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 short but contains boilerplate routing info and lacks substantive content. While concise, it fails to convey the tool's core purpose or parameters effectively.

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 delete nature and single parameter, the description is severely incomplete. Missing details on what the tool does, required arguments, output structure, and usage context. An output schema exists but is not referenced.

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 0%, and the description provides no detail on the 'arguments' parameter beyond being a JSON string. No hint about required fields (e.g., feed connection ID) or format, leaving the agent completely in the dark.

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 merely states 'delete_feed_connection' operation without explaining what deleting a feed connection entails. It relies on the tool name to convey purpose, which is insufficient for an AI agent. No explicit verb or resource description beyond the operation name.

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 on when to use this tool versus alternatives like xero_create_feed_connection or xero_list_feed_connections. No prerequisites, conditions, or exclusions mentioned.

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