pbs_tape_changer_get

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

With no annotations, the description carries the burden of behavioral disclosure. It declares the tool as READ-ONLY and notes a config prerequisite, which is helpful. However, it does not explain error handling, return value structure, or side effects, leaving gaps in transparency.

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 a single, well-structured sentence with no unnecessary words. It front-loads the read-only nature and essential config requirement, making it efficient for an agent to parse quickly.

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 simple get operation with an output schema, the description captures the core action and a key prerequisite. It does not mention the required 'name' parameter (already in schema) or contrast with similar tools, but overall it provides sufficient context for an agent to understand its role among many siblings.

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 documentation covers both parameters (name and proximo_target) completely. The description's mention of 'PROXIMO_PBS_* config' adds some context for the target parameter but does not go beyond what the schema already states. Baseline 3 is appropriate given full schema coverage.

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 PBS tape changer's config', specifying the verb 'get' and unique resource. It effectively distinguishes from sibling tools like pbs_tape_changer_list, pbs_tape_changer_create, etc., by focusing on a single config retrieval.

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 mentions it is read-only and requires PROXIMO_PBS_* config, giving basic context. However, it does not explicitly guide when to use this tool over alternatives like pbs_tape_changer_list or pbs_tape_changer_status, leaving the agent to infer usage from the tool name.

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