list_bulk_jobs

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

With no annotations provided, the description must fully disclose behavior, but it only states the action without revealing pagination semantics, response format, ordering, or any side effects. The agent is left without information about how the listing behaves.

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 and front-loaded, but it is under-specified. It does not provide enough informative content to be considered efficient; it merely echoes the tool name without elaborating on purpose or behavior.

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?

For a list tool with no output schema and no annotations, the description should explain what is returned (e.g., a paginated list of bulk jobs), how pagination works, and any relevant context. None of this is provided, leaving the description incomplete for a tool with only two optional parameters.

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% with descriptions for both 'page' and 'per_page', so the schema carries the parameter semantics. The description adds no additional meaning beyond what is already in the schema, warranting the baseline score of 3.

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 'List bulk jobs' is a direct restatement of the tool name 'list_bulk_jobs', adding no additional specificity or context. It does not clarify what constitutes a bulk job, the scope of listing, or how it relates to sibling tools like 'get_bulk_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?

No guidance is provided on when to use this tool versus alternatives such as get_bulk_job, create_bulk_job, or cancel_bulk_job. There is no mention of prerequisites, expected use cases, or exclusions.

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