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

Beyond the read-only annotations, the description discloses that saved details are frozen at save time, lists possible status values, describes included notes/media, explains vault limit usage, and flags that media URLs are private and API-key-gated. These are meaningful behavioral and access constraints that an agent would not know from annotations alone.

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 compact and front-loaded: it first identifies the vault contents and ordering, then adds privacy context and plan requirements. Every sentence carries useful information with no filler.

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 zero-parameter, read-only tool with no output schema, the description is complete enough to tell an agent what is returned, how it is ordered, what statuses exist, and what access limitations apply. No critical calling information appears to be 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?

The tool has zero parameters, so there are no parameter semantics to document and the baseline is 4. The description does not need to compensate for an input schema, and it appropriately focuses on output content and access constraints instead.

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 states a specific resource and scope: the account's saved ads in the vault, returned newest first, with frozen details, statuses, notes, media files, and plan usage. It distinguishes itself from sibling vault operations like save/remove/update by describing the stored vault contents rather than a mutation action.

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 clear prerequisites — an Indie or Agency plan, with trials counting — and warns that asset URLs require the account’s API key and must not be shared publicly. It does not explicitly name when to use this instead of vault_save, vault_remove, or vault_update, but the viewing context is clear from the description.

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