Request Vulnerability Exception

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

Annotations already indicate destructiveHint=true and readOnlyHint=false, so the agent knows this is a write operation. The description adds the 'pending' state, which is useful, but it does not explain the effects, reversibility, or what the output represents. The 'shared REST/UI/MCP lifecycle' phrase is vague and adds little behavioral detail beyond the annotations.

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 sentence with no redundancy or fluff, making it very concise. The sentence gives a clear action and object, though the lifecycle phrase is ambiguous. It is well-structured for its brevity, but the content is minimal rather than effectively enriched.

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 tool with 9 parameters and an output schema, the description is severely under-specified. It does not explain what a 'pending exception' is, when to submit one, what the response contains, or how it relates to the exception workflow. The schema covers parameter syntax, but the tool-level context needed for correct invocation is largely missing.

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 all nine parameters are documented in the schema. The tool description adds no parameter-specific meaning, which aligns with the baseline of 3 for high schema coverage. No compensation is needed since the schema suffices.

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 states a specific verb (create) and resource (pending exception), making the core purpose clear. However, it does not differentiate from sibling tools like approve_exception or list_exceptions, which would have earned a 5. The title adds vulnerability specificity, but the description itself remains generic about the exception domain.

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. Sibling tools include list_exceptions and approve_exception, but the description neither mentions them nor explains the lifecycle stage at which this tool applies. The vague phrase 'shared REST/UI/MCP lifecycle' offers no actionable usage context.

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