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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety is covered. The description adds genuine behavioral context by specifying the return payload (a complete schema.org JobPosting plus the application link), which matters since no output schema exists; it does not mention failure behavior for a missing slug.

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?

Two short sentences with zero filler: the return content is front-loaded and the argument source follows. Nothing repeats the tool name or the schema.

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 annotations covering safety and no output schema, the description supplies both the return shape and the argument provenance. Only the error case for an invalid or unknown slug is left unaddressed.

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 0% and the schema types slug as a bare string, so the description must carry the load. It usefully states that the slug comes from search_jobs, but adds nothing about format, case sensitivity, or validity beyond that origin.

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?

"One position with its full schema.org JobPosting" identifies a single-resource fetch and enumerates the returned fields (description, location, employment type, employer, application link). It is clearly distinguishable from the sibling search_jobs, though the retrieval verb is implied rather than stated outright.

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?

"Use slug from search_jobs" gives explicit context: this is the drill-down step after a search, and the slug argument originates there. It stops short of stating exclusions or what happens when the slug is unknown, so it sits just below a full when/when-not statement.

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