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

Beyond the readOnly/non-destructive annotations, the description discloses that no authentication is required (anonymous use) and that an unknown name returns a list of available names — both behavioral traits the annotations do not convey. It also states the output format (markdown/JSON, English body).

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?

Front-loads the most important constraint (no auth needed) and then proceeds through purpose, alternative, names, input, and output in labeled lines. It is dense and earns most of its length, though the bracketed auth notice and multi-line layout make it slightly heavier than necessary.

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, the description correctly supplies the return format and language. Combined with the auth disclosure and the unknown-name fallback, an agent has everything needed to call this single-parameter tool correctly.

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 coverage is 100% so the schema already documents the name parameter and its short-name/URI-path forms; per the rubric the baseline is 3. The description adds value by glossing each of the main guide names ('analysis' = business impact/dependency analysis, etc.) and by noting that an unrecognized name yields a listing, which the schema does not.

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 ('returns IceShore guide documents by name') and enumerates the guide topics (ADL writing, registration, analysis). It is clearly distinguishable from siblings like get_content or get_notes, which fetch user data rather than static documentation.

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?

Explicitly tells the agent when to use this tool ('for clients that don't support MCP resources') and names the alternative ('supporting clients can read the same content via resources/read'). It also gives the condition for an unknown name, which routes the caller to the fallback listing behavior.

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