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

Beyond the destructive annotation, the description explains the exact consequence: the application is skipped, nothing is sent to the employer, and none of the user's applications is spent. It also clearly discloses irreversibility with 'A rejection cannot be undone with these tools.'

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 front-loaded and mostly efficient: each sentence adds a consequence, caution, or routing cue. However, the 'Pass 1 to 25 application_ids...' sentence largely repeats schema content, and the final next-step sentence is useful but not essential.

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 destructive mutation tool, the description covers the important behavioral details: what rejection means, that it is irreversible, limits on batch size, and the alternative for queued applications. Since an output schema exists, return values need not be explained.

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%, and the schema already documents the application_ids range, source, and example. The description repeats the 1-to-25 and getmattered_get_applications details but does not add new parameter semantics beyond what the schema provides.

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 states a specific verb and resource: rejecting applications that are waiting for the user's review. It also explicitly distinguishes this from cancellation by naming getmattered_cancel_applications for queued or still-preparing applications.

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 gives clear when-to-use guidance ('Reject only the applications the user said no to') and explicit when-not-to-use guidance ('Do not use it to stop an application that is queued or still being prepared'). It also names the alternative tool and points to getmattered_get_matches as a next step.

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