list_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 mentions default and max limit but does not disclose behavior such as pagination, ordering, security/permissions, or whether the operation is read-only (though implied). Lacks explicit assurance of safety.

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 short and front-loaded, starting with the core purpose. It uses a clear structure: summary, clarification, then parameter details. No unnecessary words.

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?

Covers purpose, parameter details, and links to sibling get_job. However, lacks description of return format (fields, ordering) and any prerequisites or permissions. Given no output schema, more detail on return values 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?

The 'Args' section explains all three parameters with valid value lists for status and action, plus default/max for limit. Since schema coverage is 0%, the description adds significant meaning beyond the schema.

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 the verb 'List' and the resource 'VibOps operations', and distinguishes itself from sibling tool 'get_job' by specifying it retrieves full results of a specific operation. It also clarifies that VibOps jobs are not Kubernetes 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?

Provides clear context for when to use this tool (listing recent operations) and when to use an alternative ('Use get_job to retrieve the full result of a specific operation'). Does not explicitly mention when not to use it, but the purpose is clear enough.

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