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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered; the description adds ordering (newest first), per-slide return fields, and the fact that media_id is directly consumable by schedule_post and create_draft. That cross-tool interoperability is genuine behavioral context beyond the annotations. It does not mention result limits or pagination for the list mode, which is the remaining gap.

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?

Two tight sentences, front-loaded with the mode split that determines everything else, then the dependency guidance. Every clause carries information an agent would otherwise have to guess at.

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 takes on the job of describing return values and does so field-by-field for the detail mode. For a one-optional-parameter read tool this is close to complete, though the list mode's size or ordering limits are unstated.

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% and the single parameter is documented, so the baseline is 3. The description goes further by spelling out what each mode returns — a slideshow list without the id versus per-slide detail with it — which the schema only gestures at with "leave out to list them".

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 ("get ... the workspace's studio slideshows") and explicitly splits the behavior by parameter presence, so an agent immediately understands the two operating modes. It also identifies the origin of the resource (made in the Sendhour app's studio), which disambiguates it from list_posts and list_videos among the siblings.

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 forward guidance: call this before edit_slide_text, find_slide_photos and swap_slide_photo, which tells the agent it is the read-before-write step in a workflow. It does not give any when-not guidance or contrast against the listing siblings, so it falls short of a full 5.

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