export_jobs

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

With no annotations, description carries full burden. It mentions 'export to local file' but does not disclose whether this modifies server state, authentication needs, file permissions, or format specifics. The 'fmt' option is in schema but not described.

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?

Extremely concise (8 words) but lacks necessary detail for usability. It is not verbose, but underspecification makes it less helpful.

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?

Despite simple schema (2 params) and presence of output schema, the description omits critical context: output format behavior, batch limits, error handling, or file overwrite behavior. Insufficient for reliable agent usage.

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 0%, but description adds no explanation for 'ids' (job IDs?) or 'fmt' (valid values beyond default). Does not clarify what 'public job details' includes for each parameter.

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 verb (export) and resource (public job details) and indicates output (local file), but it does not distinguish this tool from sibling tools like 'get_job_details' or 'search_jobs' which might also provide job details.

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?

No guidance on when to use this tool versus alternatives (e.g., get_job_details for a single job, or search_jobs for filtering). No mention of prerequisites, file access implications, or use cases.

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