Draft a social share

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

Discloses key behaviors: rejects over-limit copy, voice lint scoring (warn-only, never blocks), and that drafts are for user review. Annotations indicate write but non-destructive, and description adds important constraints beyond annotations.

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?

Three sentences, no wasted words. Front-loaded with main action. Efficient and well-structured.

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?

Covers workflow (review via list_shares) and constraints (character limits, linting). No output schema, but description implies saved state with voice attachment. Slightly lacking return details but sufficient for agent usage.

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 50%, but description clarifies each parameter: text as copy with length rules, platform as enum, asset as gallery item. Adds meaning beyond schema defaults for project and platform.

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 clearly states it saves a draft for a gallery item, never posts, and specifies platform-specific character limits. It distinguishes from sibling 'list_shares' by mentioning review.

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?

Explicitly says when to use (save draft) and when not (no live-publish, never posts). Mentions alternative 'list_shares' for review. Provides clear context for usage.

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