deck_list

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

The readOnlyHint annotation already establishes this is a safe, non-mutating operation, so the description only needs to add context. It contributes the 'managed' qualifier and workspace scoping, but says nothing about result ordering, pagination, or whether unmanaged/external decks are excluded, which is the kind of detail annotations cannot carry.

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 wasted words, sized appropriately for a no-argument list tool. Every element (verb, resource type, scope) earns its place.

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 trivial zero-parameter read this is close to adequate, but with no output schema the description is the only place an agent could learn what a deck entry contains (id, name, slide count) or how results are ordered. The 'managed' qualifier is also left unexplained.

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 tool takes zero parameters, so there is no parameter semantics to explain and the baseline of 4 applies. The description adds nothing that could mislead about inputs.

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 gives a specific verb and resource ('List all managed PowerPoint decks') plus a scope ('in the workspace'), which clearly separates a workspace-wide deck enumeration from mutation siblings like deck_create or deck_delete. It stops short of explicitly distinguishing the read tool from other list-style siblings such as slide_list or element_list.

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 only implied: 'List all' suggests this is the entry point for discovering decks before calling deck_read or deck_update. There is no explicit statement of when to prefer this over the other list tools, no prerequisites, and no note about what happens with an empty workspace.

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