list_jobs

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

With no annotations, the description must fully disclose behavior. It states 'list' (read operation) and 'for the authenticated API key' (auth implied). However, it does not explicitly state that the tool is read-only, mention rate limits, or describe side effects. For a listing tool, this is adequate but not fully transparent.

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 extremely concise—two sentences, 12 words—and front-loaded with the verb 'List'. Every word earns its place. No unnecessary information or repetition.

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?

Given the tool has 3 optional parameters, no output schema, and no annotations, the description provides the basic purpose but lacks details about the return format, pagination behavior, or default ordering. It mentions filtering but not the limit defaults. Completeness is adequate but has clear gaps.

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 schema has 100% description coverage for all three parameters. The description mentions filtering by status or type, which corresponds to the status and type parameters, but adds no additional meaning or syntax details beyond what the schema provides. The limit parameter is not mentioned in the description. Baseline score of 3 is appropriate.

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 it lists recent screenshot jobs for the authenticated API key, with filtering by status or type. The verb 'list' and resource 'screenshot jobs' are specific. However, it does not explicitly differentiate from siblings like get_job_result or get_job_status, though the intent is clear.

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 when to use the tool (listing jobs with optional filters) but provides no explicit guidance on when not to use it or which sibling alternatives (e.g., get_job_result for a single job) are more appropriate. The usage context is clear but lacks exclusions.

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