xero_create_project

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

With no annotations provided, the description carries full responsibility for behavioral disclosure. It only mentions infrastructure routing and does not disclose that this is a mutation operation, required permissions, side effects, or return behavior. The word 'create' implies mutation but is not explicit.

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 (3 sentences) but includes irrelevant routing details that are common to the platform. It could be more concise by focusing on the purpose and leaving infrastructure to the system-level documentation.

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 lack of annotations and 0% schema coverage, the description is very incomplete. It fails to define what a project is, what parameters are needed inside the arguments JSON, or what the output schema contains. The routing info is not tool-specific.

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 'JSON string of arguments for the connector operation', which adds minimal meaning beyond the schema's type and default. With 0% schema coverage, the description should explain expected JSON structure (e.g., required keys for creating a project), but it does not.

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 'Xero connector operation create_project' and 'platform tool xero.create_project', which is essentially a tautology of the tool name. It does not explain what a 'project' represents in Xero or differentiate this from other xero_create_* tools like xero_create_asset or xero_create_invoice.

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 provides no guidance on when to use this tool versus alternatives. It only mentions routing details (JWT, tenant, scope), which are common to all Xero tools and do not inform usage decisions.

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