jobDefinition_list

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

No annotations provided, so description carries full burden. Discloses return payload contents (suspension state, override priority) which compensates for the missing output schema. However, omits critical behavioral traits: pagination behavior, read-only nature (not explicitly stated), and whether filters are optional or how they operate.

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?

Two highly efficient sentences with zero redundancy. First sentence states the action and filtering intent; second sentence details specific return values. Information is front-loaded and every clause earns its place.

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?

Adequately compensates for missing output schema by describing what data is returned (suspension state, override priority) and which entity types are included. Minor gap regarding pagination semantics, but sufficient for a list operation of this scope.

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?

Input schema contains zero parameters, establishing baseline 4 per rubric guidelines. Description mentions 'with filters' which implies parameterization, though this capability is not reflected in the empty schema object.

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?

Clear verb-resource combination ('List job definitions') with specific subtype scope ('timer and async service task definitions'). Also specifies return value fields ('suspension state and override priority'), effectively distinguishing from job_list (instances) and jobDefinition_get (single item retrieval).

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 explicit guidance on when to use this versus jobDefinition_get for single-item retrieval or jobDefinition_setSuspension for modifications. No mention of pagination behavior, result limits, or filtering prerequisites despite claiming 'with filters' support.

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