get_dataset_info

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, so the safety profile is covered; the description adds the meaningful behavioral fact that no records are read and that member summary is an optional extra limited to PDS/PDSE. It does not describe failure behavior for a missing dataset or RACF authorization errors, which would be the next useful detail.

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?

Two sentences, zero filler, with the core purpose and the returned attribute list front-loaded. Every clause carries information the agent needs.

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?

There is no output schema, yet the description compensates by naming the catalog attributes returned, which is exactly what an agent needs to decide between this and read_dataset. Minor gap: no mention of error/not-found handling or that some attributes are blank for non-VSAM datasets.

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 100%, so all three parameters are already documented, and the description's mention of the optional member summary largely restates includeMembers' schema text. Baseline 3 applies since there is no added syntax or format guidance beyond the 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?

Specific verb (Get) plus resource (catalog attributes for a dataset) and an explicit enumeration of returned fields (DSORG, RECFM, LRECL, BLKSIZE, volume). The phrase 'without reading its content' cleanly separates it from read_dataset in the sibling list.

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 'without reading its content' clause implicitly routes the agent here when only metadata is needed rather than a full read, and the PDS/PDSE qualifier scopes includeMembers. It stops short of explicitly naming read_dataset/search_dataset as the alternative for content or name lookups, and states no prerequisites for dataset access.

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