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

With no annotations provided, the description carries the burden of behavioral disclosure. It highlights the sensitive nature and required parameters, but does not expand on side effects (which are minimal for a list), response format, or data handling expectations beyond the sensitivity warning.

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 sentences front-loaded with the core purpose, with no redundant words or repetition of schema details.

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?

The tool has 7 parameters and no output schema, but the description covers the essential compliance context. However, it does not describe pagination behavior or the response structure, which might be important for an agent using this tool without prior knowledge.

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 86%, so the parameters are mostly self-explanatory. The description calls out 'reason' and 'acknowledge_sensitive_data' but merely restates what the schema already says, adding little semantic value.

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 the tool's action ('List') and resource ('Lever EEO responses with PII'), distinguishing it from the sibling tool 'list_eeo_responses' by explicitly including PII in the scope.

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 notes that this is high-sensitivity compliance data and specifies prerequisites (reason, acknowledge_sensitive_data=true), giving clear context for when to use it. However, it does not explicitly mention alternatives or when not to use it, such as referencing 'list_eeo_responses' for non-PII data, so the usage guidance remains 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.