greenhouse_reject_application

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

No annotations are provided, and the description only mentions routing and authentication details. It does not disclose that rejection is destructive, any side effects (e.g., candidate notification, status change), required permissions, idempotency, or rate limits. The description fails to inform the agent about the behavioral impact.

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 short but not front-loaded with the core action. The first sentence merely restates the name. The routing and JWT details are secondary and could be omitted or placed later. The description could be more concise by leading with the purpose.

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?

Despite having an output schema, the description does not explain what the tool returns or any error conditions. For a mutation tool, critical context like side effects, required data, and return values are missing, making it incomplete for safe agent usage.

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 only parameter 'arguments' is described as a JSON string for the connector operation, but the description does not specify what keys or values are expected. With 0% schema description coverage, the description adds no meaningful guidance beyond the schema itself.

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 mentions it is a 'reject_application' operation for Greenhouse, which implies rejecting an application, but it does not explicitly state the core action. The name is clear, but the description should directly say 'Rejects a candidate's application in Greenhouse' for unambiguous understanding.

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?

No guidance is provided on when to use this tool versus alternatives like greenhouse_advance_application. There is no context about prerequisites, conditions, or typical scenarios for rejection.

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