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

Annotations already cover the safety profile (readOnly, non-destructive), and the description adds real behavioral context beyond them: page size ('Pages hold up to 100 decks'), ordering ('newest first'), and an auth requirement ('Needs the user's Cotlet API key with access to this app'). Missing only rate/pagination cursor mechanics, so a 4.

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-loads the resource and scope, but 'newest first' is stated twice ('newest first, with folder, slide count and owner' and 'Returns decks you can open, newest first') and 'Returns decks you can open' is near-redundant with the opening. It is short but not free of waste.

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 steps in to describe the returned items (folder, slide count, owner) and pagination behavior. Combined with the auth note, an agent has enough to call it correctly, though folder/owner field shapes remain undefined.

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%, so limit, query and folder are fully documented in the schema. The description only restates the filter semantics ('Filter by title keyword or folder') and the 100-per-page cap, adding marginal meaning beyond structured data, so the baseline 3 applies.

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?

Names a specific verb+resource ('list presentations') and adds scope ('library and shared folders') plus sort order, so an agent can distinguish it from get_slides or get_presentation_analytics. It does not explicitly name a sibling it is preferred over, so it stops short of a 5.

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?

Implies usage through 'Filter by title keyword or folder' and the workflow hint 'Pass presentation_id from each item to the other tools.' However it never states when to choose this over alternatives (e.g. list_folders) or any exclusions, leaving the routing to inference.

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