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

Annotations already declare readOnlyHint=false and destructiveHint=false, so the agent knows this is a non-read-only, non-destructive operation. The description adds meaningful context beyond that: it explains that the created scope gates which tool calls are allowed and includes budgets, retry limits, and TTL. It stops short of covering auth requirements or reversibility, but the annotations carry that baseline.

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?

Three sentences, front-loaded with the core action, followed by a definitional elaboration and then a prerequisite. Every sentence earns its place with no redundancy.

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 9-parameter mutation tool with full schema coverage and annotations, the description is nearly complete: it covers purpose, scope semantics, and the critical prerequisite. It could route to related sibling tools (revoke_scope, scope_audit) to be fully complete.

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 100%, so every parameter is documented in the schema. The description adds only high-level grouping (command budgets, retry limits, time-to-live, allowed tool calls) without syntax or format details beyond what the schema already provides. Baseline 3 is appropriate.

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 uses a specific verb and resource ('Create an execution scope for a job') and immediately elaborates what a scope is ('exactly which tool calls are allowed on a kernel... with command budgets, retry limits, and time-to-live'). This distinguishes it from siblings like pcc_revoke_scope or pcc_scope_audit without needing to name them.

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?

It states a clear prerequisite: 'Required before issuing SCOPED WRITE operations (protocol upload, run create, run action).' This tells the agent when to call it, but it does not name alternatives or state when not to use it (e.g., if a scope already exists).

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