ztna_role_bindings

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

The annotations already declare readOnlyHint=true, and the description's "[READ]" prefix merely restates that. Beyond safety, it discloses nothing — no note on whether results are paginated across all bindings, whether the tenant scope is implicit from credentials, or how large result sets behave. With an annotation covering the safety profile, the remaining behavioral burden is largely unaddressed.

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?

One short, front-loaded sentence with no filler or hedging. The only redundancy is the "[READ]" tag, which duplicates readOnlyHint, but the text is not padded and reads instantly.

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 paginated listing tool with two undocumented parameters and no output schema, the description supplies too little: neither the shape of a binding nor the pagination contract is explained. An agent can invoke it, but cannot confidently interpret or exhaust the results.

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?

Schema description coverage is 0% and both parameters (page, limit) appear only as typed fields with defaults and no descriptions. The description does nothing to compensate — it never mentions pagination, defaults, or maximum limits. An agent cannot tell from either source how to page through a full result set.

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 gives a specific verb (List) and resource (tenant and collection role bindings), so an agent knows roughly what it returns. However, it doesn't clarify what a "role binding" is in this product, and it offers no differentiation from siblings like ztna_collections or ztna_users, which could plausibly expose related access data. Purpose is identifiable but shallow.

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 when-to-use guidance is given: not when to query role bindings versus collections/users directly, not whether it covers tenant-level vs collection-level scoping separately, and no prerequisites or exclusions. The agent must infer the use case from the name alone.

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