List Hedra Jobs

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

Annotations already declare readOnly/openWorld/idempotent/non-destructive, and the description adds valuable behavioral context: pagination with a cursor (next_cursor), the has_more inference, and ordering across all models. It does not describe error handling or rate limits, but for a read-only list operation it covers the key dynamic behavior well.

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 well-structured with clear sections (Args, Returns, Examples) and every sentence adds value. It avoids fluff and uses concise, actionable language.

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?

There is no output schema, but the description explicitly states the return JSON structure and how to infer has_more. It also covers pagination behavior and provides usage examples, making it complete for a list operation. The sibling differentiation adds to contextual 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 description coverage is 100% and the description essentially restates the same parameter details (limit default/max, cursor usage). It does add a small note about interpreting next_cursor for pagination, but overall it does not go substantially beyond what the schema already provides, so the baseline score of 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?

States the specific action (list jobs) with clear scope (across all models, submitted with this API key) and ordering (most recent activity first). It explicitly distinguishes itself from the sibling tool hedra_list_model_jobs by noting the all-models scope, so the purpose is unambiguous.

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?

Provides explicit 'Use when' and 'Don't use when' guidance, naming the alternative tool hedra_list_model_jobs and explaining when it is more appropriate. This gives the agent clear decision criteria for tool selection.

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