xero_back

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

The description discloses the 'no-op in flattened mode' behavior but lacks further details on side effects, permissions, or what happens in other modes. With no annotations, more depth would improve transparency.

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?

Two concise sentences that front-load the purpose and efficiently communicate key behavioral information.

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 (no parameters, no output schema), the description fully covers the necessary context, including the flat-mode nuance.

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 tool has no parameters, so the description correctly implies no input is needed. Schema coverage is 100%, and the description adds no extra parameter info, but the baseline for 0 params is 4.

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 'Return to domain selection' which is a specific verb+resource, and distinguishes itself from sibling tools like xero_navigate by noting it's a no-op in flattened mode.

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?

The description implies usage for navigating back to domain selection but does not explicitly state when to use it versus alternatives like xero_navigate, nor does it provide exclusions or context for non-flattened mode.

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