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

Annotations already declare readOnly/idempotent/non-destructive, so the safety profile is covered. The description adds two things beyond annotations: the required 'jobs:read' scope (auth requirement) and a prompt-injection warning that job text is untrusted source data, never instructions - genuinely valuable behavioral context.

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?

Four short sentences, front-loaded with the core action and return values, then retrieval mapping, then auth and safety. Each sentence adds a distinct piece of information with no padding.

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 single-parameter read tool with full annotation coverage and no output schema, the description covers return contents, parameter provenance, auth scope, and a safety caveat. Little an agent needs to call it correctly is missing.

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%, so the schema only provides type/pattern/length for job_id. The description compensates partially by explaining that the job_id is the one mapped to the customer's earlier shortlist selection, adding provenance meaning but no format or validation detail.

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 (Read) and resource (a saved job's details, original posting link, result_position), so the agent knows exactly what comes back. It doesn't explicitly name sibling tools like search_jobs or load_more_jobs to differentiate scope, but the 'saved job' framing is distinctive enough.

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?

Usage is implied via 'Retrieve the job_id mapped to the customer's earlier shortlist selection', which tells the agent the sourcing context. However, there is no explicit when-to-use versus alternatives such as search_jobs or load_more_jobs, nor any exclusions.

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