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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so the safety profile is covered. The description adds real value on top: it is free to call, it shows drafts lacking a time, and each post opens in RipClip for review, which tells the agent what happens next. The 'Free and read only' phrase partly repeats the annotations, keeping it short of 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?

Front-loads the trigger phrasings, then the behavior, then exclusions, with no filler sentences. Slightly dense in the middle where output fields, timezone format and RipClip hand-off are packed into one long sentence.

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 two-parameter read tool with an output schema and full annotation coverage, this covers everything an agent needs: triggers, exclusions, parameter ranges and formats, cost, and where the user lands afterward. Nothing required for correct invocation is missing.

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 0%, so the description carries the burden and does it well: `days` is bounded to 1-31 with a default of 7, and `timezone` is specified as an IANA identifier with a concrete example. Minor gap: the schema's UTC default for `timezone` is not mentioned.

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 ('see their posting calendar', 'shows drafts and scheduled posts') and enumerates the exact fields returned per post. It also names what it is not for, with sibling tools, so an agent can distinguish it from show_report, get_post_stats, and plan_posts immediately.

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 literal user phrasings that should trigger the tool ('what's on my calendar', 'show my drafts', 'what's scheduled this week') and a sequencing rule ('after plan_posts'). The 'Not for:' clause explicitly routes three competing intents to the correct alternatives.

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