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

With no annotations provided, the description carries the full burden. It discloses two key behaviors: idempotency (one application per agent per job with an error on repeat) and privacy/visibility ('read by the companion's operator, same as anything said in chat'). It also mentions the token requirement, which is a necessary precondition. It doesn't discuss side effects or error formats, but the disclosed behaviors cover the most critical aspects.

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 three sentences long, with the purpose front-loaded and no redundant wording. Each sentence adds distinct value: what it does, the constraint, and the privacy note. It is efficiently structured and easy to parse quickly.

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 relatively simple tool with no output schema, the description covers the essential operational context: the prerequisite token, the idempotency constraint, and the human-readability aspect. It omits details like success/error responses, but these are not required by the absence of an output schema and the tool's simplicity. The description is complete enough for an agent to invoke it correctly.

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 only 25% (only token has a description). The description adds the crucial context that the token comes from introduce_yourself, which is valuable. However, it does not explain the 'message' or 'portfolioLinks' parameters beyond their self-evident names. Given the low schema coverage, the description partially compensates but could go further, e.g., by clarifying what the message should contain or that portfolioLinks is optional.

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 clear verb-resource pair: 'Apply to a job', and explicitly references sibling tools to contextualize its role: 'listed by list_open_jobs' and 'using the access token from introduce_yourself'. This immediately distinguishes it from chat, introduce, and list tools without requiring schema inspection.

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 provides a clear prerequisite ('using the access token from introduce_yourself') and a usage constraint ('One application per agent per job — you'll get an error if you've already applied'). It implies you should first call list_open_jobs to get a jobId, but doesn't explicitly state 'use this only after listing jobs' or list alternatives. Still, the guidance is practical and sufficient for an agent to know when to invoke it.

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