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

Beyond annotations, the description discloses the concrete side effect ('Sets terminalAccessRequested, which get_me reports'), confirms idempotency in plain language ('repeating the call changes nothing'), and rules out common misconceptions (no access granted, no support ticket, no trades). This adds significant behavioral context that annotations alone do not convey.

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 three tight sentences, front-loading the core action and then adding side-effect, idempotency, limitation, and alternative information. 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 no-parameter, idempotent request action with annotations and an output schema, the description covers purpose, side effect, idempotency, non-effects, and the sibling alternative. Nothing an agent needs in order to call it correctly is 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?

The tool has zero parameters, so there is no parameter syntax or semantics to explain. The baseline for a 0-parameter tool is 4, and the description appropriately does not waste words on nonexistent inputs.

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: 'Join the waitlist for early access to the Synoptic trading terminal (beta) for the signed-in account.' It also distinguishes itself from the sibling request_feature by explicitly naming it for other product requests, so an agent can tell them apart without opening schemas.

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 explicitly names the alternative tool for other product requests ('Use request_feature for other product requests') and clarifies what this tool does not do ('Does not grant access, open a support ticket or place trades'), giving clear when-to-use and when-not-to-expect guidance.

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