job_resume

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

No annotations are provided, so the description must carry the full burden of behavioral disclosure. The description gives zero information about side effects, permissions, mutation vs. read-only nature, or return behavior, leaving the agent completely blind.

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 extremely short, but this is under-specification, not conciseness. While there is no wasted text, the single token provides no useful information, so it does not earn credit for brevity.

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?

With 13 parameters (2 required), no output schema, nested objects, and zero annotation coverage, the description is completely inadequate. An agent cannot correctly call this tool with only the phrase 'job resume'.

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%; the description mentions none of the 13 parameters. With no explanation of how parameters like 'action', 'context', or 'threshold' affect behavior, the agent has to guess from names and types alone, which is insufficient given the complexity.

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 'job resume' is a direct restatement of the tool name, providing no verb, resource, or distinguishing detail. It fails to convey what the tool actually does, leaving the agent to infer from the name alone, which is ambiguous given the 'resume' action could mean resuming a job or retrieving a resume.

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?

There is no guidance on when to use this tool versus alternatives like job_cancel or status. No context about appropriate scenarios, prerequisites, or when not to use it is provided.

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