Apex Verify Session

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

Annotations provide limited info (readOnlyHint=false, etc.). The description adds critical behavioral details: it resets the per-token request counter, enables retrying the original tool call, and is gate-immune. No contradiction with 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?

Four sentences, efficiently front-loaded with the core purpose. Every sentence adds essential information without 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?

Given the tool's simplicity (one parameter, straightforward purpose) and the presence of an output schema (not shown but indicated), the description fully covers what an agent needs to know: purpose, usage, parameter handling, and behavioral outcomes.

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% for the single 'code' parameter. The description adds value by instructing to 'submit verbatim' and noting backend matching, which goes beyond the schema description.

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 clearly states that the tool resets the Apex Copilot verification gate after obtaining a code, with a specific verb 'Reset' and resource 'verification gate'. It is not a tautology and distinguishes from sibling tools by explaining gate-immune behavior.

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?

Explicitly tells when to call ('once the user has either completed the verify procedure... and shared the resulting code'), explains the effect (counter resets, retry original call), and states the endpoint is gate-immune, providing clear usage context and exclusions.

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