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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint false. The description adds meaningful context beyond annotations by revealing the return content ('Returns field names, types, and whether they are required') and the dependency on fetch_sweepstakes. No contradictions 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?

The description is well-structured with headers and sections, but the content is redundant: the first paragraph is nearly identical to the 'When to use' section. This duplication wastes space and slightly blurs the document. Still, it is not excessively verbose.

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 one parameter and no output schema, the description is complete: it states what it returns, the required precondition, and the intended workflow position relative to other tools. No gaps linger.

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 coverage is 100% for the single parameter, with the parameter description already stating 'The sweepstakes token (UUID format)'. The tool description's Parameters section repeats exactly this, adding no new semantic value. 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 clearly states the tool's function: 'Get all form fields for a sweepstakes entry page.' It uses a specific verb+resource construction and explicitly distinguishes its role from related tools by noting it should be called before add_participant to discover required fields.

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?

Usage guidance is explicit: 'Use fetch_sweepstakes first to get the sweepstakes_token' and 'Call this before add_participant to discover required fields.' It also provides a concrete pre-call condition: 'fetch_sweepstakes if the user gave you a sweepstakes name instead of a token.'

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