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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds the shape of the returned payload (compensation, applyUrl, freshness timestamps), which is useful context, but says nothing about behavior for a missing/invalid id or any rate limits.

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?

A single sentence, front-loaded with the identity of the tool and the resource, with the return contents following. Nothing 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 usefully enumerates the key returned fields, so an agent knows what a call yields. The remaining gap is edge-case handling (invalid id), which is minor for a simple one-param read.

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 coverage is 100% and the single 'id' parameter is documented with an example, so the schema does the heavy lifting. '(from search_jobs)' adds provenance for where a valid id comes from, but no additional format or validation semantics beyond the schema.

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?

States a specific verb and resource ('Full detail for one role by id') and enumerates what the detail contains (applyUrl, compensation, skills, geography, timestamps). It also names search_jobs as the source of the id, which clearly separates it from the sibling search/list tools.

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?

The parenthetical '(from search_jobs)' establishes the workflow: call search_jobs first, then fetch a single role here. It does not explicitly exclude or compare against the other siblings (diff_since, list_orgs, market_stats), so the routing context is implied rather than spelled out.

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