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

Annotations already establish this is a safe read (readOnlyHint true, openWorldHint false). The description adds genuine value beyond them by disclosing the return format (Markdown) and the internal structure of the returned document (problem, work, outcome), which helps the agent anticipate the response.

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 tight sentence with no filler, and the core resource and its return format are front-loaded. Every clause (Markdown format, the three content sections) carries information.

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 one-parameter read tool with full schema coverage and safety annotations, the description covers return format and content shape well. It lacks explicit routing to list_projects, the only remaining gap for an agent choosing between the two.

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% and the slug parameter is fully documented with an enum of valid values and a pointer to list_projects. The description adds nothing about the parameter, which is acceptable given the schema does the heavy lifting, 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?

The description states a specific resource (one case study) and its return format (Markdown), plus the content sections it contains (problem, work, outcome). The verb is only implied by the tool name, and it doesn't explicitly name the list_projects sibling it contrasts with, so it's clear but not fully differentiated on its own.

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?

'One case study' implies single-item retrieval as opposed to the listing behavior of list_projects, which gives an agent a usable hint. However, there is no explicit when-to-use/when-not statement or named alternative, so the guidance is only implicit.

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