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

With no annotations, the description carries the behavioral disclosure burden. It adds useful context by distinguishing tracked/scored employers from the not-yet-ingested pipeline, which is more than a bare list would provide. However, it omits details like pagination, ordering, result size limits, or whether pipeline entries include scores.

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 a single sentence that front-loads the main resource ('All employers') and then adds necessary scope qualifiers. Every phrase earns its place, with no repetition or 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?

For a simple no-parameter list tool, the description covers the main output categories: tracked employers with Transparency Scores and the pipeline. However, since there is no output schema, details about returned fields, pagination, or how pipeline entries are represented are left unspecified.

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 has zero parameters, so there is nothing for the description to clarify beyond what the empty schema shows. The baseline of 4 applies because parameter semantics are not a concern.

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 clearly identifies the resource (employers tracked by Fair Session) and the scope: all tracked/scored employers plus the pipeline of identified-but-not-yet-ingested ones. It does not explicitly state the action verb 'list,' but the tool name and phrasing 'All employers...' make the purpose evident.

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?

The description gives context but no guidance on when to choose this tool over siblings like get_employer_score or check_offer. It does not state what this tool is not for or when a more specific tool should be used.

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