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

Annotations already declare readOnlyHint/openWorldHint/destructiveHint=false, so the safety profile is covered. The description adds useful non-obvious behavior: results are limited to the authenticated user's own shots, ordering matches the profile, pagination flows through next_cursor, and it requires a Cotlet API key with app access.

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?

Front-loaded and scannable, but the field list ('title, tags, publish date and URL') and the 'newest first' ordering are stated twice, making the second sentence largely redundant. Trimming that repetition would tighten it without losing 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?

With no output schema, the description carries the return-shape burden and does so by listing the fields and pagination mechanism, plus the auth prerequisite. It is essentially complete for a simple paginated list tool, with only the minor redundancy as a blemish.

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 100% (limit and cursor both documented), so the baseline is 3. The description adds genuine semantics for cursor by explaining the next_cursor round-trip, though it says nothing extra about limit beyond the schema's '1 to 100, default 24'.

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 and resource ('list shots'), scopes it ('your own shots, newest first, same order as your profile'), and enumerates the returned fields (title, tags, publish date, URL). It also names downstream siblings (get_shot_stats, list_comments, update_shot) so an agent can place it precisely among Dribbble tools.

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?

Gives clear context for how to use the output ('use the shot_id of an item in get_shot_stats, list_comments and update_shot') and how to paginate ('pass next_cursor back as cursor'). It stops short of stating when NOT to use it or naming a competing list alternative, but there is no obvious sibling to disambiguate against.

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