xero_create_time_entry

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

No annotations are provided, so the description carries full burden. It mentions generic routing but does not disclose behavioral traits such as mutability, permissions, side effects, or rate limits. Even basic information that this tool creates a record is implied but not explicitly stated.

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 very short, but it is underspecified rather than concise. It does not earn its keep; every sentence is generic and fails to convey essential information. Better to have no description than one that is merely a tautology.

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 no annotations, zero schema description coverage, and a single opaque parameter, the description is severely incomplete. It does not even state the basic purpose of creating a time entry. An output schema exists but is not referenced in the description, adding no value.

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 only parameter, 'arguments', is described as a 'JSON string of arguments for the connector operation', which adds negligible meaning. With 0% schema description coverage, the description should compensate but provides no details on expected structure, keys, or examples, leaving the agent with no semantic understanding.

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 merely restates the tool name as 'Xero connector operation `create_time_entry`', which is tautological. It does not explain what a time entry is or what creating one does, failing to provide a specific verb+resource distinction. Compared to siblings like 'xero_list_time_entries', it offers no differentiation.

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 given on when to use this tool versus alternatives. There is no mention of prerequisites, context, or conditions under which this tool should be avoided. The description lacks any usage direction.

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