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

With no annotations, the description carries the full burden. It discloses that the sync hits live external APIs, hinting at network behavior, but says nothing about the required API key, rate limits, latency, idempotency, or whether metrics are written back to storage versus merely fetched — all material for a sync trigger.

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?

A single tight sentence with the triggering action front-loaded and the platform list as useful scope. It is well-sized, though the parenthetical platform list is somewhat expendable.

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 low-complexity tool with 2 optional flat parameters and no nested objects, the description is minimally adequate. However, with no annotations and no output schema, it should state whether the sync persists results, how long it takes, and when it should be preferred over reeling_get_analytics.

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 api_key ('Optional Reeling API key') and post_id ('Optional post UUID') are already documented in the schema. The description adds no meaning beyond that and never mentions either parameter, 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 ('trigger') and resource ('on-demand real-time metric sync') and enumerates the platforms it operates against, so the action is clear. It fails to differentiate from the sibling reeling_get_analytics or reeling_get_post_status, leaving the read-vs-refresh boundary for the agent to guess.

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?

'On-demand' and 'live APIs' imply this is a user-triggered refresh rather than a passive cached read, which is weak implied guidance. There is no explicit when-to-use statement, no exclusion of the analytics/status siblings, and no note that post_id narrows the sync to one post.

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