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

Annotations already declare readOnly, idempotent, non-destructive, closed-world behavior, so the bar is lower. The description still adds real scope information: only *published* projects are retrievable and the payload includes description and public links. It omits behavior for a nonexistent or unpublished slug, which is the remaining gap.

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 with no filler: the action, the identifier requirement, and the returned fields each carry weight. Nothing is padded or repeated.

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 single-parameter read tool with no output schema, the description covers the operation, the input constraint, and the returned content, while annotations carry the safety profile. Only the miss case (slug not found or unpublished) is undocumented.

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 0% and the only parameter's schema is just a pattern and length bound. The description contributes that the slug match is exact, which is genuinely useful over the raw regex, but adds no format examples, casing rules, or failure semantics for a mismatched slug.

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?

Specific verb (Retrieve) plus resource (published project) and the key constraint (exact slug), which implicitly separates it from search_projects' fuzzy lookup. It never names the siblings outright, so an agent must infer the routing rather than being told it.

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?

"By its exact slug" implies this is the tool for when you already know the identifier, whereas search_projects would be for discovery, but that condition is left to inference. No explicit when-to-use, when-not-to-use, or named alternative is stated.

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