Get Jobs

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

Annotations already declare readOnlyHint=true and idempotentHint=true, establishing the safety profile. The description adds domain context (jobs as workflow execution instances) but does not disclose behaviors like pagination, filtering semantics, or result ordering. Overall it provides minimal additional behavioral transparency beyond the annotations.

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 concise and front-loaded with the core action. The supporting sentences define jobs in domain terms, which is useful context but not essential for invocation. It earns its place without being verbose.

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 simple list tool with two optional filters and an output schema, the description adequately explains the domain and purpose. It lacks usage guidelines and does not mention filtering, but the schema covers parameters and the annotations handle safety. It is complete enough for invoking the tool correctly.

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% for both parameters, and the schema descriptions are clear. The description does not add any parameter-specific guidance, and its phrase 'Get all jobs' slightly obscures the optional filtering by name or project, though this is not a contradiction.

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 states 'Get all jobs from Itential Platform' with a clear verb and resource, and explains what jobs are. However, it does not distinguish this from related tools like describe_job or get_job_metrics, which focus on specific aspects of jobs.

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. The description only explains what jobs are and emphasizes monitoring, but it does not state exclusions or compare with sibling tools such as describe_job or get_job_metrics.

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