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

Annotations already mark the tool read-only and idempotent. The description adds behaviors not covered elsewhere: a fallback role list for employers with fewer than 3 roles, candidate lists for ambiguous names, case and 'Inc.' insensitivity, a stated date window, a linked company page, and treatment of employer text as untrusted data.

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?

The description is dense and front-loaded, and every clause carries information. The long run-on list in the first sentence is somewhat hard to scan, but nothing is wasted.

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?

There is no output schema, so the description compensates by detailing the returned fields, the fallback cases and the links. That is thorough for a single-parameter read tool.

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 coverage is 100%. The description still adds matching semantics the schema lacks: case and 'Inc.' suffixes are ignored, and an ambiguous name returns candidates rather than an error.

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?

The description says the tool returns one employer's open developer roles from its company page facts block. It enumerates the contents: 7-day role count, locations, types, levels, salary coverage and range, hiring system, pace, skills and newest roles. The single-employer focus separates it from search_jobs, weekly_summary and salary_summary.

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 implied: call this when you want a profile of a named employer. Siblings are never named, and there is no guidance on when to prefer search_jobs or salary_summary. The note that employers with fewer than 3 roles get a role list instead is useful conditional behavior, but it is not selection guidance.

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