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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the description only needs to add behavioral detail. It does add value by enumerating the returned payload (revenue figures, products, chains, token_status, source link, date), which matters since no output schema exists. It says nothing about what happens when the slug is unknown or when the project actually has a token.

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 compact sentence with the resource and scope front-loaded and no filler. The parenthetical sits mid-sentence rather than being separated out, but nothing is wasted.

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 with no output schema, enumerating the return fields covers most of what an agent needs, and the annotations cover safety. Missing are error/not-found behavior and the exact meaning of token_status, but the core is present.

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%, so the single 'slug' parameter is undocumented in the schema itself. The description partially compensates by naming its origin ('from tc_projects'), but gives no format, casing, or example, leaving the agent to guess at valid input.

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 concrete verb and resource ('One coinless project by slug') and pins the scope to token-less projects, which separates it from tc_get_token and the listing tool tc_projects. The word 'coinless' is odd jargon, but the parenthetical source makes the intent recoverable.

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 parenthetical '(from tc_projects)' hints that slugs originate from the tc_projects sibling, which is useful routing. It never states explicitly to use this instead of tc_get_token when a project does have a token, so the when-not case is left to inference.

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