list_scopes

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It does not mention whether this is a read-only operation, what data it returns, whether it requires special permissions, or any side effects. The description adds zero behavioral insight.

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 extremely short, but this is not conciseness—it is under-specification. It provides no value and fails to convey essential information. A helpful description would be brief yet informative; this one is just empty.

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 the tool has 9 parameters, no output schema, no annotations, and no meaningful description, it is completely inadequate for an agent to understand what the tool does, when to use it, or how to invoke it correctly. Nothing about the context is covered.

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%, so the description must compensate by explaining the parameters. It does not. With 9 parameters (2 required) and no explanations, the agent cannot infer what values to provide or what each parameter means. The description is completely silent on parameter semantics.

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 'list scopes' is a tautology that merely restates the tool name. It does not define what a 'scope' is, what the tool does with them, or how it differs from sibling tools like list_domains or list_contexts. The verb 'list' is generic and the resource 'scopes' is undefined.

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 any of the many sibling tools. No mention of prerequisites, typical use cases, or alternative tools. The agent is left entirely without direction.

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