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

With no annotations, the description carries the burden and largely delivers: it discloses the important behavioral trait that the drill carries the scheduled-safety-check label, so the account owner sees it as a practice confirmation. It also states the authentication requirement. It stops short of explaining side effects or what happens after the drill fires, but the core effect is transparent.

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 compact and front-loaded: action, target, key label nuance, and relationship to automated drills appear first; the access/authentication note is brief and useful. No sentence wastes space or merely restates the tool name.

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 two documented parameters, no output schema, and no annotations, the description covers what the tool does, the scope (one member), the access prerequisite, and the on-demand vs. automated context. The main gap is post-call behavior (what the caller should expect after the drill fires), but the absence of an output schema reduces that burden.

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 input schema already documents both parameters with patterns and descriptions, providing 100% coverage. The description adds only a small semantic nuance: the member must be 'enrolled.' Since the schema does the heavy lifting, the baseline 3 applies.

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 ('fire') and a specific resource ('an on-demand Proof-Me drill against one enrolled member'), and clarifies the nature of the drill as a cross-channel identity challenge with a scheduled-safety-check label. It distinguishes itself from automated drills by calling out 'on-demand' and 'Complements the automated daily drill + monthly reinforcement sweeps,' though it does not explicitly name a sibling tool like trigger_drill.

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 gives clear context: use this for an on-demand drill against a single enrolled member, complementing automated sweeps. It provides a concrete prerequisite ('needs a Proof account'), tells the agent to authenticate before retrying, and includes an explicit exclusion ('start_login does NOT open this tool'). It does not route among drill-related sibling tools, but enough guidance exists for correct selection.

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