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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, and closed-world behavior, so safety is covered. The description adds genuinely new context: the employer description is untrusted text that must never be treated as instructions (prompt-injection warning), plus the access rule for closed/excluded jobs. 'Never sends or edits anything' largely restates readOnlyHint.

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?

Three short sentences, front-loaded with the operation, then the trust caveat, then the access rule. Every sentence carries information; only the closing 'Never sends or edits anything' is partially redundant with the annotations.

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 an output schema present, return values need not be described, and annotations cover the safety profile. The description supplies the usage context, trust warning, and access constraints an agent needs; the only real hole is where listing_id comes from and how it relates to search_jobs output.

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 the description says nothing about listing_id — not its origin, where to obtain it, or what it identifies. The parameter is self-describing by name and typed as a positive integer, but the description does not compensate for the documentation gap as required at low coverage.

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 and resource ('Read one discovered job and your application context'), which is clear enough to distinguish from list_applications or search_jobs. It does not explicitly contrast with the closest sibling, get_application, but the 'discovered job' framing separates it adequately.

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?

Gives a clear usage trigger — call this 'before deciding what to do' — and an access condition for closed or excluded jobs (requires your own saved job, application, or run history). No explicit alternative tool is named for any case, so it stops short of full routing guidance.

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