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

Annotations already declare it is a non-idempotent write to an external system (readOnlyHint=false, openWorldHint=true), so the safety profile is covered. The description adds genuine extra context: the external-integration prerequisite and the fact that summary and notes are the transmitted payload. It stops short of noting failure modes or duplicate-send risk.

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 with zero padding; the action and payload are front-loaded and the constraint follows immediately. Nothing redundant with the title.

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 9-parameter write tool with no output schema, the description covers purpose, payload, destinations, and the connectivity prerequisite, which is close to what an agent needs. Missing only any note about return/confirmation behavior or what a failed send looks like.

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 89%, so the schema already documents seq, target, mindmap, language, location, shownotes, transcripts, and mix options in detail. The description adds nothing about any parameter (e.g. target values, Reader-only fields), so the baseline 3 applies.

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 (the summary and notes of a transcribed episode) plus destinations (Notion database or Readwise Reader). It is distinguishable from sibling export/markdown tools by naming the actual payload and the two target services, though it doesn't explicitly contrast with send_clips.

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?

Provides a prerequisite (the integration must already be connected in Podwise settings), which is useful context for when the call will succeed. However, it gives no guidance on when to prefer this over send_clips, export_episode_markdown, or the enterprise export tools, and no exclusion conditions.

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