preview_registration

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

The description discloses that it is non-destructive (preview only), returns a summary, conflicts, and a fingerprint, and that the fingerprint is required for confirmation. This is sufficient given no 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 concise, front-loads the purpose, and uses a list to detail the parameter structure without any unnecessary words.

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?

It covers input structure, output summary (summary, conflicts, fingerprint), and links to the sibling tool confirm_registration, providing adequate completeness despite lacking output schema details.

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?

With 0% schema coverage, the description fully explains the 'actions' parameter structure (array of objects with action, subject_code, optional section), adding critical meaning beyond the raw schema.

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 'Preview add/drop actions WITHOUT submitting', which uses a specific verb and resource, and distinguishes from the sibling 'confirm_registration' which actually submits.

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 indicates usage before confirmation by mentioning the fingerprint needed for confirm_registration, though it does not explicitly state when not to use or provide alternatives.

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