list_job_tasks

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

With no annotations present, the description carries the full behavioral burden. It does disclose one genuine precondition (Workflow module required) and the read-only nature is implied by 'List', but it says nothing about permissions, pagination limits, result volume, or what happens with an invalid job_id.

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?

Three short sentences, front-loaded with the action and the entity disambiguation, then filters, then the hard prerequisite. Nothing is padded or restated.

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 five-parameter list tool with no output schema and no annotations, the description covers purpose, filters, and the module prerequisite without exposing the return shape. The main remaining gap is return-format/pagination expectations, which the schema partially addresses via page/pageSize defaults.

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%, so all five parameters (job_id, name, status, page, pageSize) are already documented in the schema with defaults. The description only echoes the name/status filters and adds no matching semantics (e.g. whether name is a substring match, or valid status values), so baseline 3 applies.

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?

States a specific verb and resource ('List the tasks for a specific job') and usefully disambiguates the term 'job' as Project/Engagement, which many agents would otherwise misread. It does not, however, contrast itself with nearby siblings such as get_job or update_task_status, so an agent still has to infer the boundary from the name.

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 names the two available filters and states the prerequisite ('Requires the Workflow module'), which is real usage guidance. It gives no explicit when-to-use/when-not-to-use rule and never names an alternative tool (e.g. get_job for the job itself), so routing remains implied rather than directed.

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