List Deploy Runs

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

Annotations already declare readOnlyHint=true and openWorldHint=true. Description adds important behavioral details: the read-only nature is reinforced with 'INSPECTION' and 'List', and it specifies return content. Also notes the session_id must be passed exactly as returned, which is critical. No contradictions.

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?

Four well-organized sentences: bolded purpose, return fields, use cases, prerequisite. No redundant or vague phrasing. Every sentence adds value.

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?

A simple read-only list tool with one parameter and no output schema. Description covers purpose, prerequisites, returned fields, and use cases. Could mention pagination or limits, but not necessary given simplicity and annotations.

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% and the schema description already thoroughly documents the session_id parameter (format, requirement to include token). The tool description adds only a brief mention of 'session_id from convoopen response', which does not significantly exceed schema detail. 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?

Starts with 'INSPECTION: List all Terraform deployment runs for a session', clearly indicating the action and resource. Specifies returned fields (job IDs, statuses, types, timestamps), distinguishing from sibling tools like tflogs or tfstatus.

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?

Explicitly lists use cases: view deployment history, find job IDs for log inspection, check success/failure. States prerequisite (session_id from convoopen). Does not explicitly mention when not to use or alternatives, but context is sufficient.

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