pbs_tape_media_content

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

The description explicitly declares READ-ONLY behavior and hints at adversarial data (guest-influenced fields), which adds transparency beyond no annotations. However, it does not disclose pagination, error cases, or authorization details, leaving gaps for a 7-parameter tool with no annotations.

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 concise (three lines) and front-loaded with the key action 'list media content'. Some jargon ('ADVERSARIAL') may confuse, but overall it is efficient and avoids unnecessary verbiage.

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?

Given the output schema exists, the description does not need to detail return values. It mentions a config requirement (PROXIMO_PBS_*) and draws a parallel to pbs_snapshots_list. However, it lacks completeness for a tool with 7 parameters and many siblings, missing guidance on result structure or filtering nuances.

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 100%, so baseline is 3. The description mentions 'snapshot' and 'label-text' but does not enhance understanding of parameters beyond what the schema already provides (e.g., backup_id, label_text). No new semantic value is added.

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 clearly states the tool lists media content (snapshot inventory recorded across tape) and marks it as READ-ONLY. However, it does not explicitly differentiate from sibling tools like pbs_tape_media_list or pbs_snapshots_list, which weakens its distinctiveness.

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?

The description provides no explicit guidance on when to use this tool versus alternatives. It briefly mentions 'ADVERSARIAL' and a requirement for PROXIMO_PBS_* config, but lacks when-not or comparative context among the many tape/snapshot related siblings.

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