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

The description claims the tool mutates nothing ('without mutating status or email state'), but the annotations set readOnlyHint=false, which indicates the tool is not read-only. This is a direct contradiction, and per the rubric behavioral transparency must be scored 1 with an annotation contradiction flag.

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 that front-loads the core purpose and the safety guarantee. There is no filler or repetition beyond the title, and every phrase adds relevant context.

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?

This is a complex 10-parameter tool with no output schema and no parameter descriptions, yet the description only states that it is a non-mutating preview. It does not explain the expected preview output, how the parameters shape the preview, or what follow-up tool should be used to actually apply the change.

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 0%, and the description provides almost no parameter-level semantics beyond naming the statuses 'Interviewing' and 'Offer' and the concept of email. With 10 parameters and 5 required ones, the description fails to compensate for the absent schema documentation.

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 a specific action—'Preview'—and a specific resource: the applications-owned Interviewing-to-Offer status/email approval POC. It distinguishes from mutating sibling tools by saying it operates 'without mutating status or email state,' though it does not name a specific alternative.

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?

The description implies a preview-before-apply workflow but gives no explicit when-to-use guidance, prerequisites, or mention of the sibling apply/bind tools as alternatives. An agent must infer that this is the safe preview counterpart to a mutating operation.

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