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

No annotations are provided, so the description carries the burden. It doesn't explicitly state that the tool is read-only or has no side effects, but as a 'get' tool with no parameters, this is implicit. It doesn't mention response format, errors, or other behavioral traits, which is acceptable for such a simple operation but not thorough.

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 sentence that efficiently lists the tool's scope. The most important content (migration paths, promises, pricing, audience) is front-loaded and there is no filler. Every word earns its place.

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 parameterless getter with no output schema, the description adequately conveys what the tool returns. It could mention that it provides a summary or overview, but the enumerated aspects make the purpose clear. The tool is simple enough that no additional context is strictly needed.

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?

The tool has zero parameters, and the schema coverage is 100% vacuously. Per the rubric, a baseline of 4 is appropriate when there are no parameters to describe. The description doesn't need to add parameter semantics.

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 clearly states the tool retrieves the public offering of IIS Rescue, listing specific aspects (migration paths, promises, pricing, target audience). This is a specific verb+resource and differentiates from siblings like get_migration_paths and get_partner_channel by scope, though it doesn't explicitly name them.

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 on when to use this tool versus the sibling get_* tools. The description only describes content, leaving the agent to infer that this is for an overview while others are for details. No explicit exclusions or conditions are given.

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