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

Annotations already establish read-only, idempotent, non-destructive behavior. The description adds useful context by saying the data is saved and that no provider work is triggered, though it does not discuss filtering scope or pagination behavior.

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?

The description is two short sentences with little waste and the key read-only/no-provider-work constraint is front-loaded. The first sentence is a noun-phrase fragment rather than a full purpose statement, but it remains efficient.

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 tool with seven filter parameters, no output schema, and low schema-description coverage, the description leaves important invocation details unstated. It says what data is returned and one downstream use, but it does not explain filtering, pagination, or sibling selection.

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 only 29% across seven parameters, and the description does not explain url, area, days, limit, offset, direction, or workspace semantics. It mentions action IDs as outputs, not how to use the input filters, so it does not compensate for the schema gaps.

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?

The description identifies the resource clearly: saved owned-page action IDs, source evidence, and preparation states. It is specific about contents, but it does not explicitly distinguish this plural listing tool from siblings like read_preparation_action or read_prepared_page_changes.

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?

It gives one concrete downstream usage: use an action ID with prepare_page_changes. It also clarifies that the read triggers no provider work, but it does not explain when to choose this tool over the singular action reader or the prepared-changes reader.

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