read_member

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

With no annotations provided, the description carries the disclosure burden. It communicates that the operation is a read and returns text, but does not mention behavior on missing members, encoding, or any preconditions like an active connection. 'Read' implies no mutation, though the description does not explicitly confirm side-effect-free behavior.

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 two purposeful lines with no filler. The core behavior is front-loaded, and the Args section directly supports the only parameter.

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 one-parameter read operation, the description covers the essential input format and purpose, and an output schema exists so return-value details need not be repeated. It does not mention prerequisites such as an established connection or what happens when the member does not exist, but these are minor for such a simple 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 description coverage is 0%, so the description must supply parameter meaning. It does so by specifying the expected PDS.NAME(MEMBER) form for pds_member, which is essential and not present in the schema. It stops short of giving examples or formatting details, but the single-parameter case is well addressed.

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 uses a specific verb ('Read') and resource ('PDS member') and clarifies the output format ('as text'), making the tool's purpose unambiguous. This also differentiates it from sibling tools like list_members and list_datasets, which operate on collections rather than a single member's contents.

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 purpose statement implies when to use the tool: when the contents of one PDS member are needed as text. However, it does not explicitly state when not to use it or name alternatives such as list_members for discovering members, leaving usage context to inference.

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