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

With no annotations, the description carries the full burden. It usefully discloses that only public projects are returned, and 'Read' implies a non-mutating operation, but it says nothing about behavior on a missing/private slug or what authentication, if any, applies.

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 eight-word sentence with no filler, front-loading the verb and resource so the agent grasps the operation immediately.

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-one getter this is adequate minimum-viable coverage, but with no annotations and no output schema, the description should at least indicate the error behavior for an unknown slug or what the returned card contains.

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?

Only one parameter exists and schema coverage is 0%, but the description supplies the key semantic the schema lacks: the slug is the lookup key for a single project card. That is meaningful, though it adds no format, casing, or validation detail beyond minLength.

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 (Read), resource (project card), and scope (one, public, by slug), which separates it from the sibling list_live_projects that returns many. It does not name a sibling explicitly, so it stops short of the top band.

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 phrase 'by slug' implies you call this when you already have a single project identifier, but there is no explicit when-to-use, prerequisite, or pointer to alternatives such as list_live_projects for discovery.

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