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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety and scope are covered without the description's help. The description adds one useful behavioral fact — that results are summary entries paired with a top pick tool — but says nothing about result count, ordering, or pagination.

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 sentence with zero filler, front-loaded on the action and resource, with the parenthetical examples earning their place by anchoring the abstract term 'job guide'.

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 zero-parameter read-only list tool with no output schema, the description covers what it is, what comes back (guides plus a top pick tool), and roughly how many domains exist via examples. It stops short of noting that no filtering or pagination is supported, which is the only remaining gap.

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?

The tool takes zero parameters, so the baseline is 4 per the rubric. The description correctly implies no input is required, matching the empty schema, and there is no parameter complexity to misrepresent.

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 (List) and resource (Coghelm's job guides) with concrete examples (1:1s, board updates) that make the domain tangible. The phrase 'each with its top pick tool' also signals this is a summary/browse view, which implicitly separates it from the singular sibling get_job_guide.

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: a browse-list naturally precedes a detail fetch, so an agent can infer it should call this before get_job_guide. However, the description never names get_job_guide or states an explicit when-to-use condition, and there are no exclusions.

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