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

No annotations are provided, so the description must disclose behavioral traits. It only states the tool lists jobs, but omits whether it is read-only, any rate limits, pagination behavior beyond schema defaults, or error handling. The minimal description shifts the burden onto the schema, which also lacks detail.

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 a single sentence of 9 words, efficient and to the point. However, it may be too terse given the missing details; it could include a brief note about the return format or pagination defaults without losing conciseness.

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 no output schema and no annotations, the description is incomplete. It does not explain what the tool returns (e.g., list of job objects or IDs), how pagination works beyond defaults, or the exact filtering behavior. The agent would lack critical context to use the tool effectively.

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?

With only 33% schema description coverage, the description should add meaning to the parameters. It mentions 'pagination' and 'optional status filtering' but does not clarify the page/limit parameters beyond what the schema already provides (defaults, min). The status parameter is described in the schema, so the description adds no new semantics.

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 tool lists 'async simulation jobs' with pagination and optional status filtering, which is a specific verb-resource combination that distinguishes it from sibling tools like cancel_job, submit_job, or get_job_status.

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 for listing jobs but does not provide explicit when-to-use or when-not-to-use guidance. There are sibling tools like get_job_status and get_job_result that serve different purposes, but no alternatives or exclusions are mentioned.

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