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

readOnlyHint=true already establishes this as a safe read, so the description's main added value is the 'published' qualifier, which hints that non-published listings are not retrievable. It does not describe error behavior for unknown slugs or any rate/pagination limits, so it stays at baseline against the annotations.

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, wasting nothing. The tail is a long enumerated list of returned fields, which is informative but slightly list-heavy for one sentence.

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 enumeration of returned data (FAQ, pricing, platforms, screenshots, verified store/GitHub data, agent-readiness checks) usefully compensates. The only real gap is the slug-vs-listing-ID mismatch and no guidance on missing/invalid slugs for a single-required-param tool.

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 description coverage is 0%, so the description must carry parameter meaning; it does indicate the slug identifies a published listing, which is helpful. But it claims lookup 'by slug or listing ID' while the schema accepts only a single 'slug' string, creating ambiguity about what value to pass.

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') and a precise, singular resource ('one published listing'), and enumerates the payload (description, FAQ, pricing, platforms, verified store/GitHub data). It clearly distinguishes itself from the plural sibling list_projects and from get_submission/get_badge.

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 singular 'one published listing' implies this is the detail-fetch counterpart to list_projects, which is useful implicit routing. However, there is no explicit when-to-use/when-not statement, no mention of what happens for unpublished or unknown slugs, and no direct naming of an alternative.

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