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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world, so the safety profile is covered. The description adds genuine behavioral context beyond that: the description field is HTML, stages come back in order with the inbox first, and each stage carries an application count and its applicant-facing email. That is real value about the shape of the result.

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?

One compact sentence with no filler, and the payload contents are listed immediately. It reads as a run-on enumeration rather than a front-loaded verb statement, but nothing in it is redundant.

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 no output schema, the description must explain what comes back, and it does so thoroughly for a single-entity read tool: content, format, ordering, and aggregate counts. Combined with annotations covering the safety profile and a fully documented ID parameter, an agent has everything needed to call 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?

There is a single parameter with 100% schema coverage, including a detailed UUID format and the note that it comes from list_jobs. The description adds nothing about the parameter, so the baseline 3 applies when the schema does all the work.

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 names the resource (a job) and enumerates exactly what is returned: details, HTML description, application form, and ordered stages with per-stage application counts and applicant emails. This is specific enough to distinguish it from get_application or list_jobs, though the phrasing is a noun fragment with no verb and no explicit sibling contrast.

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 statement of when to call this versus get_overview, get_stats, or list_jobs, and no note that a jobId must first be obtained from list_jobs. The only pointer to the ID source lives in the input schema, not the description, so the description offers no usage guidance at all.

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