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

"Read-only" merely restates the annotations, which already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so it adds no credit. Nothing is said about behavior beyond the annotations: what happens when account_id or job_id does not resolve, whether the caller needs account-scoped permissions, or what fields come back.

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 words contain no filler, and the resource is front-loaded, but the terseness crosses into under-specification rather than efficiency. Two fragments are not a structure that supports correct invocation.

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?

It is a simple read tool with no output schema, so some burden is lifted, but with zero parameter documentation and an unexplained nested "extra" object the definition is not sufficient on its own. An agent could form a call but not understand scope, error behavior, or how to use extra.

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?

Three parameters at 0% schema description coverage and the description explains none of them. account_id (uuid) and job_id are undocumented, and the open-ended nested "extra" object is entirely unexplained, so the description does nothing to compensate for the coverage gap.

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 job post" names the resource and implies single-record retrieval, which does contrast implicitly with the plural sibling list_job_postings. But it is a sentence fragment with no verb (fetch/retrieve), so the agent must infer that this returns a job posting rather than operating on one.

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?

No when-to-use guidance is given at all, and no alternative is named. The singular/plural split with list_job_postings can be guessed from names, but the description itself provides no condition or exclusion to route the agent.

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