xero_contacts_search

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

The description discloses that it returns contacts matching a substring search, but lacks details on pagination, case sensitivity, maximum results, or response structure. Since no annotations exist, the description carries the full burden and provides basic but incomplete 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?

The description is two sentences, front-loaded, and contains no extraneous information. Every word adds value.

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?

For a simple search tool with one parameter and no output schema, the description covers the essential behavior. It could mention that multiple contacts may be returned or specify case sensitivity, but it is adequate for the complexity level.

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 description coverage is 100% for the 'term' parameter, and the tool description adds no additional meaning beyond what the schema provides. The baseline is 3, as the description does not enrich parameter understanding.

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 searches contacts by name and returns those whose name contains the search term. It distinguishes from sibling tools like xero_contacts_list (list all) and xero_contacts_get (get by ID) by specifying the search-by-name functionality.

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 name-based searching but does not explicitly state when to use this tool versus xero_contacts_get (for exact ID lookup) or xero_contacts_list (for retrieving all contacts). No guidance on limitations or prerequisites is provided.

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