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

With no annotations provided, the description carries the full burden. It mentions 'anonymous' and 'compliance reason' but does not disclose operational traits such as read-only nature, permission requirements, pagination behavior, or response content. 'Use carefully' is a vague warning that adds little concrete behavioral information for a sensitive compliance tool.

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 two short sentences, each earning its place. The first sentence states the purpose with a clear verb and resource; the second adds a necessary caution. It is front-loaded and free of unnecessary wording.

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?

Without an output schema or annotations, the description leaves gaps: it does not explain the expected return format, pagination behavior (though the `cursor` parameter hints at it), or how to choose between this tool and `list_eeo_responses_with_pii`. The 'compliance analysis' context is useful but the tool's overall usage context is not fully complete for a sensitive endpoint.

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 high (83%), with detailed descriptions for most parameters. The description does not add parameter-specific information beyond what the schema already provides; for example, the `reason` parameter's role is already described as 'Compliance reason for reading anonymous EEO responses.' Thus, the description meets the baseline without needing to compensate.

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 states a specific action ('List'), resource ('anonymous Lever EEO responses'), and context ('for compliance analysis'). It also distinguishes from the sibling tool `list_eeo_responses_with_pii` by using 'anonymous', signaling this is the non-PII variant.

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 cautions to 'Use carefully and only with an appropriate compliance reason' but does not explicitly state when to use this tool over `list_eeo_responses_with_pii` or other list tools. The 'anonymous' qualifier implies non-PII contexts, but alternatives are not named, so guidance is implied rather than explicit.

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