xero_get_organisation

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

The description mentions routing and authentication scope (JWT, tenant, company) but does not disclose whether the operation is read-only, idempotent, or has any side effects. With no annotations, this is insufficient.

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 concise with three sentences, but it lacks actionable content. It front-loads routing info that may be irrelevant for selection.

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?

Despite having an output schema, the description does not indicate what the tool returns (e.g., organisation name, address). The agent cannot fully determine if this is the correct tool for the task.

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 for the connector operation, but no details about expected structure or keys are given. Schema description coverage is 0%, yet the description adds minimal insight.

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 essentially restates the tool name ('get_organisation') without explaining what it retrieves or its value. It does not clarify that it fetches organisation profile details, making it a tautology.

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 like xero_list_accounts or xero_get_invoice. There is no mention of prerequisites or context.

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