Get a sample set by PSS ID

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

The annotations already declare readOnlyHint and openWorldHint, so safety behavior is covered. The description adds substantive context about the returned record, including participant counts, ancestry, cohorts, phenotyping details, and follow-up information, though it does not explain how the full/fields parameters change the payload.

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 front-loaded sentence with no filler. It puts the primary action and identifier first, followed by a compact summary of returned data.

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 that there is no output schema, the description usefully summarizes the response contents. The input schema fully documents projection controls, though the description could have connected full/fields to the described return payload; otherwise it is complete for a simple read-by-ID 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 100%, so the schema already documents pss_id, full, and fields thoroughly. The description reinforces the PSS ID format with an example but adds no additional meaning for the full or fields parameters, matching the baseline for high 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 uses a specific verb and resource: 'Retrieve one sample set by PSS ID.' It also names the identifier format and enumerates the record contents, making it clearly distinguishable from sibling list/search tools such as search_sample_sets.

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 phrase 'by PSS ID' implies this tool should be used when a PSS ID is already known, and the example reinforces the expected format. However, it never explicitly says when not to use it or points to search_sample_sets for discovering IDs, so the guidance is implied rather than explicit.

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