xero_list_project_users

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

No annotations are provided, so the description must disclose behavioral traits. It only mentions routing through JWT/tenant/company scope but does not indicate whether the tool is read-only, requires specific permissions, or what happens on error. The presence of an output schema is not leveraged.

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) and structured with a header and args line. However, the brevity comes at the cost of missing essential details, so it is not optimally informative.

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?

For a list tool with one parameter and an output schema, the description is incomplete. It does not explain the expected arguments, the return value, or any constraints. The output schema exists but is not referenced or summarized.

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 input schema has one parameter 'arguments' of type string. The description labels it as 'JSON string of arguments for the connector operation' but does not specify what arguments are expected (e.g., project ID). With 0% schema description coverage, the description adds minimal meaning beyond the schema.

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 names the operation 'list_project_users', which is somewhat clear, but it does not explicitly state that it lists users for a project. The title is null, and the description merely repeats the operation name without providing a verb+resource statement.

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 other Xero list tools (e.g., xero_list_projects, xero_list_contacts). There is no differentiation from sibling tools, and no context about prerequisites or alternative tools.

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