xero_navigate

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

No annotations are provided, so the description carries the full burden. It discloses the tool's primary behavior (returns tool names and descriptions), clarifies it is non-prerequisite, and implies it is a read-only, informational tool. It does not describe detailed side effects or failure modes, but given the tool's simple, no-side-effect nature, the disclosure is adequate.

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 two sentences with no fluff. The first sentence states the purpose, and the second clarifies usage context. All information is essential and front-loaded, making it highly concise and well-structured.

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?

The tool is simple with one parameter, fully documented by the schema. The description states the output (tool names and descriptions) and clarifies the help/discovery nature. There is no output schema, but the return value is adequately described. For a discovery tool, this is complete.

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 input schema already provides 100% coverage, including a detailed description for each enum value of the 'domain' parameter. The tool description adds minimal extra semantic context beyond saying it returns tools for the selected domain. Since the schema is thorough, the description does not need to compensate; the baseline of 3 is appropriate.

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's function: 'Discover available Xero tools by domain' and specifies the output ('Returns tool names and descriptions for the selected domain'). The verb 'Discover' and resource 'available Xero tools by domain' are specific, and it distinguishes itself from sibling tools by being a help/discovery aid rather than a specific Xero operation.

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 provides clear context that this is a discovery tool, noting 'All tools are callable at any time — this is a help/discovery aid, not a prerequisite.' This tells the agent it is for exploring available tools and explicitly states it is not a required precursor to other calls. However, it does not explicitly state 'use this when you need to find a tool' but that is strongly implied by the first sentence.

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