xero_agent_org_profile

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

No annotations are present, so the description must convey behavioral traits. It implies a read-only operation ('Get'), but does not disclose any additional behavioral details such as authentication requirements, side effects, or error conditions. The description is neutral but insufficient given the lack of annotations.

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 a single sentence of 10 words, highly concise and front-loaded with the core purpose. However, it could include more detail without sacrificing conciseness, such as clarifying the required parameter.

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 that an output schema exists, the description does not need to explain return values. However, with a required parameter and zero schema documentation, the description is too minimal. It is barely adequate for a simple 'get' tool but lacks completeness regarding the essential parameter.

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?

Schema description coverage is 0%, meaning the schema provides no documentation for the 'xero_tenant_id' parameter. The description does not explain what this parameter is, where to obtain it, or its format. It fails to compensate for the missing schema descriptions, leaving the agent to infer from the parameter name alone.

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 a specific verb 'Get' and identifies the resource as 'Xero org profile' with concrete examples of included data (chart of accounts, tax rates, branding). It clearly states what the tool retrieves, though it does not differentiate from sibling tools like 'xero_get_organisation'.

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 explicit guidance on when to use this tool versus alternatives. Usage is implied: when you need org profile information. There are no exclusions or context provided to help an agent decide between this and similar tools.

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