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

With no annotations, the description carries the full burden. It implies a read-only list but says nothing about pagination, ordering, default filtering, whether the status filter is optional, or what gets returned.

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 front-loaded sentence with no wasted words. Brevity is appropriate to the tool's small surface, though it edges into under-specification rather than tight conciseness.

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 2-parameter list tool with no annotations and no output schema, the description leaves the status parameter, return shape, and pagination behavior entirely undocumented. An agent cannot reliably call it with a status filter based on this text.

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 50%: product_id is documented in the schema (with a pointer to list_products), but status has no description and no enum. The description does not compensate at all — it never mentions the status filter or its accepted values.

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 (List) and resource (staged content opportunities) scoped to a product, which is distinguishable from siblings like list_drafts, list_seeds, and list_jobs. It does not explicitly contrast with those siblings, but the resource noun is specific enough for an agent to pick it.

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?

No guidance on when to use this versus list_drafts, list_seeds, or list_jobs, and no prerequisites or exclusions. The word 'staged' hints at a lifecycle state but the agent is left to infer it.

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