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

Goes well beyond the annotations by disclosing the default destination ('Saved'), the de-duplication behavior (re-saving keeps one item and updates its note), the 100-item collection cap, and cost ('Free on every plan'). This corroborates idempotentHint/destructiveHint with concrete operational detail an agent could not infer.

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 action and trigger, then organizes the remainder under 'What to save', examples, and return shape with no filler. It is dense but each element (combination rules, examples, limits) carries information useful for correct invocation.

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 8 all-optional parameters and no output schema, the description supplies exactly what is missing: kind inference rules, valid input combinations, default collection, the return shape, and the 100-item limit. Nothing needed to invoke it correctly is absent.

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 already 100%, but the description adds real meaning the schema cannot: the valid combinations (indicator+place=value, indicator+scope=ranking, indicator alone, place alone, topic, publisher) and that 'kind is inferred when left out', plus additional scope values beyond the single schema example.

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 ('Save a statistic page to one of the user's collections') and scopes it with a clear trigger condition. It is unambiguously distinguishable from siblings like list_collections and get_collection, which read collections rather than add items.

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 a clear situational trigger ('when they ask to keep, bookmark or save it') and states the default behavior when no collection is supplied. It does not explicitly say when NOT to use it or name an alternative tool, so it stops short of a full 5.

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