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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description usefully adds the required scope (instances:read) and the nature of the returned content, but says nothing about line limits, default tail size, or that only the tail (not the full log) is available.

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 naming the resource first, then the content, then the auth need. No filler, nothing redundant with the schema or annotations.

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 simple read-only log fetch with full schema coverage and annotations covering safety, the description is nearly sufficient: it says what the log contains and what scope is needed. An explicit note on truncation/default tail would make it complete.

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%, so instance_id and tail (with its default 200 and max 1000) are already fully documented. The phrase 'last lines' hints at tail semantics but adds no format or limit detail beyond the schema, so the baseline 3 applies.

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 the specific resource (a server's container log) and the exact content returned (last lines, boot progress, app start-up, errors), which an agent can distinguish from metadata siblings like get_instance. The verb is only implied by the name rather than spelled out, but the scope is unambiguous.

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 only guidance is the permission prerequisite 'Needs instances:read.' There is no statement of when to reach for this tool versus get_instance or get_account, and no exclusions. The troubleshooting context is inferable but never stated.

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