get_job_contacts

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

With no annotations, the description carries the burden of behavioral disclosure. It explains the return type (JSON string) and mentions pagination parameters, but does not explicitly state that the operation is read-only and safe. It is clear and non-misleading, earning a high score.

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 concise with a clean docstring format: one sentence for purpose, then Args and Returns sections. It is front-loaded and efficient, though the Args could be slightly more streamlined without losing clarity.

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 description covers the main purpose, all parameters, and the return type. Since an output schema exists, detailed return field documentation is not needed. However, it lacks information on error handling or behavior when job_id is invalid, which would enhance completeness.

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 input schema has 0% description coverage, so the description fully compensates. It explains each parameter: job_id as required, limit as max contacts (default 50), and offset as pagination skip (default 0). This adds significant meaning beyond the schema's bare properties.

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 action 'Get all contacts/candidates associated with a job', which is a specific verb-resource pairing. It differentiates from siblings like 'get_contact' (single contact) and 'list_contacts' (all contacts) by specifying the association with a job.

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 implies usage when retrieving contacts for a specific job, but it does not explicitly state when to use this tool over alternatives like 'list_contacts' or 'get_contact'. No guidance on exclusions or prerequisites is provided.

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