vercel_get_deployment_logs

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

No annotations exist, so the description must disclose behavioral traits. It only states 'Get logs', implying a read operation, but does not mention pagination, real-time following (though a 'follow' parameter exists), rate limits, or the format of log entries. This is insufficient for a tool with 5 parameters.

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 a single short sentence with no filler. However, it is so concise that it omits potentially useful context. It earns a 4 for efficiency but loses a point for under-specification.

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?

With no output schema, no annotations, and 5 parameters, the description is quite sparse. It does not explain the nature of logs, how to interpret them, or any constraints like maximum limit. This is inadequate for an agent to reliably use the 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?

All 5 parameters have descriptions in the input schema (100% coverage), so the baseline is 3. The description adds no additional meaning beyond the schema; it does not explain the order or format of logs returned.

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 'Get logs for a specific deployment' clearly states the verb 'Get' and the resource 'logs for a specific deployment', which is distinct from sibling tools like 'get_deployment' (which returns deployment metadata) and 'list_deployments' (which lists deployments).

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?

No guidance is provided on when to use this tool versus alternatives, or any prerequisites or when not to use it. The description is a single sentence without any context for appropriate usage.

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