Contract Testing: Admin List Permissions

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and idempotentHint=true, indicating a safe read operation. Description adds no extra behavioral context beyond stating it's admin-level, which is already in the title.

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?

Description is short but includes redundant items like 'Toolset: Admin' and 'Parameters: None', which do not add value beyond the first sentence and title. Could be more streamlined.

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 parameters and no output schema, the description is minimal but does not describe the output format or how results are structured, which could be helpful for a listing tool.

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?

Input schema has zero parameters, so description does not need to explain parameter meanings. Stating 'Parameters: None' is sufficient and matches schema coverage of 100%.

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?

Description clearly states 'List all available permission scopes (admin)'. The verb 'list' and resource 'available permission scopes' specify exactly what the tool does, distinguishing it from sibling admin tools that create, delete, or manage roles/users.

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?

Adequate for a simple listing tool with no parameters. It implies usage when needing permission scopes for admin tasks, but lacks explicit guidance on when to use vs alternatives or contextual prerequisites.

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