xero_contacts_list

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

Without annotations, the description must disclose behavioral traits. It mentions pagination and optional filtering, which implies a read-only, batch operation. However, it does not specify side effects, permissions, rate limits, or that it returns a list. The parameter descriptions in the schema confirm pagination limits (100 per page), so the description adds marginal behavioral context.

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: first states the action and core feature (pagination), second covers optional filtering and return fields. No redundant or filler content.

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 no output schema, the description usefully specifies return fields. For a simple list tool with pagination and optional filter, it covers the essentials. However, the presence of sibling xero_contacts_search suggests that guidance on when to use list versus search would enhance completeness. Error handling and data freshness are not addressed.

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?

Input schema has 100% coverage with clear parameter descriptions for 'page' and 'where'. The description adds value by stating that results include 'name, email, and addresses', which is not in the schema (no output schema). This extra context justifies a score above the baseline of 3.

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 uses specific verb 'List' and resource 'contacts in Xero', clearly indicating a paginated listing operation. It distinguishes from sibling tools like xero_contacts_get (single contact) and xero_contacts_search (likely full-text search) by mentioning pagination and optional where clause filtering.

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 says 'Optionally filter using a where clause', implying use cases for filtered or unfiltered lists. However, it does not contrast with sibling tools like xero_contacts_search, which might be more appropriate for complex queries. No explicit when-not-to-use guidance is provided.

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