xero_create_folder

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

With no annotations, description carries full burden, but only mentions routing and authentication basics. Omits destructive nature, success/failure behavior, rate limits, or side effects.

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?

Short but includes unnecessary routing details. Could be more concise by focusing on the folder creation function rather than API mechanics.

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 an output schema (unseen), the description lacks return value explanation and fails to specify what constitutes a folder creation request. Leaves agent without essential context.

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?

Single parameter 'arguments' is a JSON string with 0% schema description coverage. Description only says 'JSON string of arguments for the connector operation', adding no meaningful structure or required fields for creating a folder.

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?

States verb 'create' and resource 'folder', but lacks specificity. Does not clarify what a folder represents in Xero (e.g., in Files module) or distinguish from sibling tools like clio_create_folder or smokeball_create_folder.

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 on when to use this tool versus alternatives. Among many Xero tools and other create_folder tools, the description provides no context for selection.

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