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

Annotations already declare readOnlyHint=false, idempotentHint=false and openWorldHint=true, so the agent knows it mutates external state. The description adds the connection prerequisite but omits the meaningful non-idempotent behavior (e.g. whether re-sending duplicates clips) and any success/failure outcome.

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 sentences, front-loaded with the action and destinations, followed by the prerequisite. No filler.

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 and no nested objects, the definition covers what an agent needs to invoke it — target, selection mode, and the gating prerequisite. Minor gap around error handling and idempotency, but nothing blocking.

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 only 67% (target enum is undocumented), but the description compensates by explaining the clipId/episodeSeq semantics — one clip versus all ready clips of an episode — which the schema alone does not convey.

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 (send) and resource (clips) and names both destinations (Notion/Readwise) plus the two selection modes (clipId vs episodeSeq). It does not differentiate from the sibling send_episode, which an agent may confuse with this tool.

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?

Adds a real prerequisite — the integration must already be connected in Podwise settings — which is useful context. However it gives no guidance on when to prefer send_clips over send_episode or export_clips_markdown, leaving that routing to inference.

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