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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=true, covering the safety profile. The description adds useful context ('Logs may contain application data'), a data-sensitivity warning beyond annotations, but says nothing about pagination, retention window, or return format.

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 compact sentences, front-loaded with the core action, and the second sentence earns its place as a data-sensitivity caveat. It is perhaps overly terse for a 10-parameter tool, but there is no waste.

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?

For a tool with 10 parameters, 0% schema coverage, and no output schema, two sentences are insufficient. The description omits any explanation of the numerous injected beon_* fields or what a caller receives, leaving meaningful gaps an agent cannot close from structured data.

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 0% across 10 parameters, so the description carries the full burden and fails to compensate: it names no parameter, and the eight beon_* infrastructure fields (context, resume_id, release_id, environment, connection_id, etc.) are entirely undocumented anywhere. 'Authorized deployment' only loosely gestures at deployment_id.

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 and resource ('Read runtime logs') scoped to 'an authorized deployment', which is distinguishable from the many other vercel_* tools. However, it does not differentiate itself from the close sibling vercel_get_build_events, so an agent must still infer which log type to select.

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 'for an authorized deployment' hints at a prerequisite, but there is no explicit when-to-use/when-not guidance and no mention of the alternative log-retrieval sibling (vercel_get_build_events). The agent is left to infer selection context.

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