Get an annotated screenshot set

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

With no annotations present, the description carries the full behavioral disclosure burden. It usefully discloses that results are ordered and human-reviewed, which adds context beyond 'get screenshot set'. However, it does not mention output format, error behavior for unknown slugs, or any access considerations.

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?

The description is a single, front-loaded sentence with no filler. It puts the verb and object first, then the scoping detail, and every word contributes useful 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 no output schema, the description covers the essential context: what is returned (annotations), their nature (ordered, human-reviewed), and scope (one app slug). Lacking only detailed return-value structure and edge-case behavior, which are minor for this simple operation.

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?

The schema provides only a bare 'slug' string with no description, so schema coverage is 0%. The description adds minimal meaning by identifying the slug as a 'niceapps.club app slug', but it does not explain slug format, valid values, or how to obtain one; the single parameter is simple enough that this is adequate but not strong.

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 clearly states a specific verb ('Return') and resource ('ordered, human-reviewed screenshot annotations') scoped to one app slug. It does not explicitly contrast with sibling tools like search_screenshots, but the noun phrase 'screenshot annotations' distinguishes this from raw screenshot retrieval.

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?

Usage is implied rather than explicit: the description tells the agent this tool returns annotations for one specific niceapps.club app slug, suggesting it is appropriate when a slug is already known. It does not provide any when-to-use vs. when-not-to-use guidance or mention sibling alternatives.

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