list_answers_for_application

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

With no annotations provided, the description carries the full behavioral burden and it only declares 'Read-only'. That is a useful safety signal for a mutation-free tool, but no other traits (pagination, scope of 'demographic responses', auth needs) are disclosed. Adequate but thin.

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?

Two short parts with zero waste; the purpose is front-loaded ahead of the workflow hint. Efficient, though very terse.

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?

An output schema exists so return values need no explanation, and the single-param signature is simple. The discovery workflow for application_id fills the main gap; minor behavioral detail (pagination) is the only omission.

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% and the single parameter is documented as the Greenhouse application ID, so the baseline is 3. The description goes beyond the schema by explaining how to derive that ID via a chained lookup, adding real meaning.

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'), resource ('demographic responses') and scope ('for a specific application'). This distinguishes it from the generic list_answers sibling, though it doesn't explicitly name that sibling for contrast.

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?

Provides an explicit discovery workflow for obtaining the required application_id (search_candidates_by_name → list_applications → match to job), which is genuinely actionable. It doesn't state when to prefer this over list_answers or get_eeoc_for_application, but the context is clear.

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