ztw_list_roles

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

The description repeats the read-only trait already declared by readOnlyHint=true and adds no new behavioral context such as pagination, auth requirements, result format, or filtering side effects. openWorldHint=false is also not explained in the description.

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, front-loaded sentence with no filler or unnecessary detail. It is about as concise as possible for stating the core action and resource, though the redundancy of 'read-only' with annotations is minor.

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 having six optional parameters and no output schema, the description offers no information about return shape, filtering behavior, or the meaning of the include flags. The query parameter schema provides some context, but the tool description itself is too sparse to be considered complete for complex use.

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 description mentions none of the six parameters and does not help map semantics beyond the schema. With schema description coverage at only 17%, the description fails to compensate for the largely undocumented parameters; the only rich parameter documentation lives inside the query field's schema description, not in the tool description.

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 clearly states the action ('List') and the exact resource ('ZTW admin roles'), and explicitly notes it is read-only. This distinguishes it from sibling tools like ztw_list_admins, which target a different resource.

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?

There is no guidance on when to use this tool versus alternatives, no exclusions, and no contextual examples. The description only restates the resource and read-only nature, leaving the agent to infer usage from the tool name.

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