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

No annotations exist, so the description carries the full disclosure burden, and it does volunteer a real behavioral trait beyond the schema: the visibility boundary that other bidders' proposals are never returned. It also effectively documents the return payload since no output schema exists, though it says nothing about permissions or error behavior.

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 tight sentence, front-loaded with the verb and resource, followed immediately by the return contents and the scope boundary. No sentence is filler.

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 correctly spends its words enumerating return fields, and with no annotations it also supplies the read-only/visibility context. It is complete enough for a simple id-based getter, leaving only minor gaps (auth expectations, error/empty cases).

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 100% and both parameters (job_id, plus the deprecated api_key) are documented in the schema itself, so the baseline is 3. The description adds no format or constraint detail beyond implying a single-job lookup by id.

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 precise verb ('Get') and a singular resource ('one job') and enumerates the returned payload: spec, budget, status, bid count/lowest/median bid. The singular scope plus the exclusion ('Never other bidders' proposals') separates it from the plural-fetching sibling jobs_search without needing to open either schema.

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 only implied: the required job_id makes clear this is the lookup tool when you already know which job you want. It names no alternative and gives no when-not-to-use condition (e.g., 'use jobs_search when you don't have an id'), so the routing guidance stops at inference.

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