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

No annotations are provided, so the description carries the full burden. It discloses the read-only nature ('List') and the specific attributes the results carry, such as licenses, archive digests, pinned environments, and unrun evidence status. It does not mention output format or pagination, but for a zero-parameter read-only list tool this is reasonably transparent.

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 entire description is a single, front-loaded sentence with the verb first and every clause adding meaningful scope or result detail. There is no redundancy or filler.

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 tool's low complexity (zero parameters, no nested objects, no output schema), the description covers the essential context: what is listed and what kind of information the results expose. It could mention output shape or explicitly name the singular get_starter_study alternative, but those are minor omissions for this 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?

The tool has zero parameters, so there is no parameter burden for the description to carry. The baseline score of 4 applies because the schema already makes it clear that no arguments are needed.

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 begins with a specific verb ('List'), identifies the resource ('original downloadable source studies'), and adds scoping attributes (explicit licenses, archive digests, pinned catalog environments, unrun evidence status). This clearly distinguishes it from siblings like get_starter_study or list_task_templates.

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 the tool is for enumerating starter studies rather than fetching a single one or listing task templates, but it never explicitly states when to choose this tool over get_starter_study or list_task_templates. Usage is inferred from the verb 'List' rather than stated.

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