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

With no annotations supplied, the description carries the full disclosure burden. It does reveal the payload shape (full description plus LLM scoring reason, implying a heavier read than a list view), but says nothing about what happens when the hash is unknown, whether the read is cheap or expensive, or whether scoring is always populated.

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?

There is no wasted wording, and the payload information is front-loaded. But it is a bare fragment rather than a structured sentence, and brevity here comes at the cost of missing essentials rather than through efficient expression.

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?

The tool is simple (one required param, no output schema, no nesting), yet the description leaves the sole required identifier undefined and gives no guidance about sourcing it from sibling tools. For a lookup-by-key tool, that gap is material.

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% and there is one required parameter, dedup_hash, whose format and provenance (where the agent obtains such a hash) are entirely unexplained. The description adds no meaning beyond the parameter name, so the agent cannot construct a valid call from this definition alone.

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?

"Single job with the full description and the LLM scoring reason" identifies the resource (one job) and what payload comes back (full description, scoring reason), which implicitly distinguishes it from the plural fetch_jobs. However it is a noun fragment with no verb, so the action (retrieve by id) is only inferable from the tool name.

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 guidance on when to call this versus fetch_jobs, search_jobs, or vibe_top. The agent must guess that this is the single-record lookup used after a list/search returns an identifier, and nothing states prerequisites or error behavior.

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