xero_get_purchase_order

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

No annotations are provided, so the description must carry the full burden. It only mentions routing details (JWT, tenant, company scope), which are generic and not specific to this operation. Key behavioral traits like idempotency, error handling, or permissions are absent.

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 short but wastes space on tautology (restating the tool name) and irrelevant routing details. The parameter description is too brief. It could be more concise and informative.

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 has one parameter and an output schema (not shown), the description should clarify input requirements and expected return. It fails to explain what 'arguments' should contain, leaving a critical gap for agent invocation.

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 single parameter 'arguments' is described as a 'JSON string of arguments for the connector operation.' With 0% schema description coverage, this adds minimal meaning. The agent is not told what keys or values to include (e.g., a purchase order ID), making it difficult to use correctly.

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 states it is a 'get_purchase_order' operation, indicating retrieval of a purchase order. However, it does not specify whether it retrieves by ID or other criteria, and fails to distinguish from siblings like xero_list_purchase_orders. The purpose is vague but not misleading.

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_purchase_orders, xero_create_purchase_order). There is no information about prerequisites or context, leaving the agent without decision support.

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