xero_list_contact_groups

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

No annotations are available, so the description must fully disclose behavioral traits. It mentions routing details but fails to state whether the operation is read-only, destructive, or requires specific permissions. A listing tool likely requires read access, but this is not confirmed.

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 brief and front-loaded with the core function. It uses only three sentences to convey purpose, routing, and parameter hint. It could be more structured but remains efficient and to the point.

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?

An output schema exists, so return values are covered externally. However, the description lacks context about what contact groups are, how the 'arguments' parameter should be structured, and any prerequisites or side effects. It is minimally viable for a simple listing tool.

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 a single generic 'arguments' parameter (a JSON string) with 0% description coverage. The description merely restates this as 'JSON string of arguments for the connector operation,' adding no specific meaning or valid argument structure for listing contact groups.

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 lists contact groups via a Xero connector operation. It includes the platform tool name and routing path, making the purpose explicit. However, it does not differentiate from sibling tools like xero_list_contacts, which list contacts rather than groups.

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., xero_list_contacts, xero_list_invoices). The description lacks explicit when-to-use or when-not-to-use context, leaving the agent to infer usage from the name alone.

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