get_study_details

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

With no annotations, the description details the return structure but does not disclose any side effects, authentication needs, or rate limits. However, for a read-only 'get' operation, the transparency is adequate.

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?

Well-structured with clear sections: description, usage tips, returns. Every sentence adds value, and it is front-loaded with the purpose.

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 single parameter, no annotations, and detailed return description, the tool definition is complete for its purpose. The description covers all necessary aspects.

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?

Input schema has 100% description coverage for the single parameter 'study_accession'. The description adds no additional semantics beyond the schema's description and examples.

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 it 'Get comprehensive metadata for a specific ENA study including publications.' It specifies the verb, resource, and scope, distinguishing it from siblings like 'get_study_publications' which only returns publications.

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?

Provides explicit usage tip: 'Call after search_rna_studies() to verify a study matches your research needs before downloading.' It also mentions checking publications array for PubMed IDs, giving clear context for when to use.

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