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

Annotations already declare readOnlyHint=false, idempotentHint=false, destructiveHint=false and openWorldHint=true. Beyond those, the description adds genuinely useful scope limits: it is agency-owned, sourced only from existing roster creators, and cannot handle image/cover uploads. It omits auth/permission specifics and any side effects, so not a 5.

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 with zero filler; the operation and its most important constraint are front-loaded.

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?

An output schema exists, so return values need not be explained, and the annotations cover the mutation safety profile. The description supplies the roster-source constraint and the upload limitation; the only gap is what happens when referenced creators are not in the roster.

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 description coverage is 100%, so all 13 parameters are self-documented and the baseline is 3. The description adds no parameter-level detail (e.g., how creator_ids order or visibility/password interaction works) beyond what the schema already provides.

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 (Create) and resource (agency-owned pitch deck) and scopes the source of content to 'creators already in the authenticated agency roster.' This is clear enough to separate deck_create from deck_get/deck_update/deck_list, though no sibling is explicitly named.

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?

States a prerequisite (content comes from the authenticated agency roster) and an explicit exclusion ('Image and cover uploads are not supported'), which steers the agent away from expecting media handling. It does not, however, name the alternative tool to use for uploads, so it stops short of full when/when-not routing.

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