pbs_tape_media_status_get

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

The description clearly warns that the endpoint may return null despite expecting data ('best-effort passthrough', 'ADVERSARIAL'), which is valuable behavioral context. Since no annotations are provided, the description carries the full burden and does well.

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 relatively short and front-loaded with the core action, but the inclusion of technical jargon ('ADVERSARIAL', 'best-effort passthrough') makes it slightly dense. Still efficient for the information provided.

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 existence of an output schema (context signals indicate true), the description adequately covers the tool's read-only nature, config requirement, and caveats about return data. It lacks details on return fields but is sufficient for a status tool.

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% with clear parameter descriptions (uuid links to pbs_tape_media_list, proximo_target explains multi-target config). The description adds a mention of config requirement but does not significantly enhance beyond schema.

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 'get one medium's current status' and labels it READ-ONLY, distinguishing it from sibling tools like pbs_tape_media_list (list all media) and pbs_tape_media_status_set (set status).

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 implies usage for fetching status of a single tape medium but does not explicitly state when to use versus alternatives or provide exclusions. The 'ADVERSARIAL' warning hints at cautious use but is not a clear guideline.

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