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

Annotations declare this is a non-readOnly, destructive, openWorld operation. The description discloses that it syncs/stores data from an external system, which aligns with openWorldHint and the destructive/write nature. It doesn't detail the exact effects of storing (overwrite vs merge) beyond 'store them', so a small gap remains.

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 operation and immediately followed by the usage condition. No wasted words.

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 an output schema present and a single well-described parameter, the description covers the essential 'what' and 'when'. However, it omits behavioral details like whether syncing overwrites existing stats or whether it may fail under certain conditions, which could matter for a destructive operation.

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 the parameter is fully documented in the schema. The description adds no additional parameter semantics beyond what the schema provides, fitting the baseline 3.

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+resource: 'Sync the writer's Medium stats from Medium and store them, then return them.' It also distinguishes itself from the sibling get_platform_analytics by clarifying that it fetches fresh data rather than reading stored data.

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 names the condition for use: 'when get_platform_analytics reports no stored Medium stats, or the writer asks for fresh numbers.' This routes the agent correctly against the sibling read tool.

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