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

Annotations already declare readOnlyHint=true, so the safety profile is covered. The description adds nothing beyond restating the purpose and the raw REST path — no indication of log size, truncation, tailing, or whether the log is complete or partial.

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 short sentences with the purpose front-loaded and no filler. The API-path sentence is somewhat redundant for an agent but is compact and does not bloat the definition.

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 read-only GET with four fully documented required ids and no output schema — the essential shape is covered. Still missing context an agent would want: whether the log is truncated, how large it may be, and how it differs from the related status/deployment tools.

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 100% with all four ids documented in the schema, so the baseline is 3. The description adds no syntax, format, or ordering hints beyond what the schema already provides.

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 ('Get a deployment's output/log') and even pins the underlying Forge v2 endpoint. It distinguishes itself functionally from forge_get_deployment_status (status) and forge_get_deployment (metadata), though it never names those siblings 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?

Usage is implied by the resource: call this when you need the deployment's log output rather than its status or metadata. However, there is no explicit when-to-use/when-not guidance and no routing to the closely related sibling tools like forge_get_deployment_status or forge_get_deployment.

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