get_jobs

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

No annotations are provided, so the description carries the full burden. It only says 'Get all jobs' with no information about pagination, ordering, date ranges, or whether filters are exact match. It adds domain context but no behavioral traits beyond the obvious read operation.

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 front-loaded with the primary action in the first sentence. The two supporting sentences explain what jobs are, which is useful but slightly generic. No wasted words, but not maximally concise.

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?

The description covers what jobs are and the list purpose, but lacks details on filter behavior or potential limitations (e.g., pagination, default limits). An output schema exists, so return values are covered, but for a tool with no annotations, more behavioral context would improve completeness.

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 both parameters clearly described in the schema ('Workflow name used to filter the results', 'Project name used to filter the results'). The description adds no additional parameter context, so the baseline 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 'Get all jobs from Itential Platform' with a specific verb and resource, and differentiates from siblings like describe_job (single job) and get_job_metrics (metrics) by focusing on the full list of execution instances.

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 monitoring workflow execution ('provide visibility into workflow execution and enable monitoring'), but gives no explicit when-to-use guidance or alternatives. It does not mention distinguish from describe_job or get_job_metrics, making it only moderately helpful.

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