get_deployment_logs

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

With no annotations, the description must carry the safety/behavior burden; 'Fetch' implies a read-only operation and it usefully discloses that both runtime and build log streams are returned. However, it says nothing about log retention, truncation/pagination, or permissions, which matters for a diagnostic tool.

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?

A single front-loaded sentence with the resource and purpose stated up front and zero filler. Nothing to trim.

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 and no annotations, so the description is the only source of behavioral context, and it omits return shape, log volume/limit interaction, and error behavior. Adequate but leaves real gaps for a two-parameter diagnostic tool.

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% (deployment_id and limit both documented), so the schema does the heavy lifting and the baseline is 3. The description adds no format or meaning beyond the schema, and the runtime/build distinction is not mapped to any parameter.

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 a specific verb (Fetch), resource (runtime and build logs), and scope (a specific Vercel deployment), plus the diagnostic intent. It is distinguishable from siblings like analyze_logs and get_recent_errors, though it does not name an alternative explicitly.

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?

The phrase 'to diagnose deployment failures' gives an implied use case, but there is no guidance on when to prefer this over analyze_logs, get_recent_errors, or get_error_details, and no prerequisites are stated.

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