encode-toolkit

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

Annotations provide readOnlyHint=false (write operation), openWorldHint=true (external data fetching), idempotentHint=true (safe to retry), and destructiveHint=false (non-destructive). The description adds valuable context beyond annotations: it explains what gets stored (experiment metadata, publications, pipeline info), mentions the local SQLite database, compares to Endnote for papers, and notes this is required for downstream tools. It doesn't contradict annotations and provides meaningful behavioral details.

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 well-structured and front-loaded: first sentence states the core purpose, followed by detailed explanation, analogy, usage guidelines, and parameter/return details. Every sentence adds value with no redundancy. The bullet-point style for Args and Returns enhances readability without wasting space.

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 complexity (write operation with external fetching, 4 parameters, annotations, and output schema), the description is complete. It explains purpose, usage context, parameters, returns, and relationships to other tools. With output schema present, it doesn't need to detail return values, and the annotations cover safety/behavioral traits. No gaps remain for agent understanding.

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 carries full burden. It provides detailed parameter explanations: 'accession' with an example ('ENCSR133RZO'), 'fetch_publications' and 'fetch_pipelines' with their purposes and defaults, and 'notes' with its optional nature. This adds significant meaning beyond the bare schema, fully compensating for the lack of schema descriptions.

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 the specific action ('Track an ENCODE experiment locally') and resources involved ('experiment metadata from ENCODE', 'local SQLite database', 'publications', 'pipeline/analysis information'). It distinguishes from siblings by emphasizing local storage and library-building functionality, unlike tools like encode_get_experiment (fetch without storage) or encode_export_data (export existing tracked data).

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 explicitly states 'WHEN TO USE: Use to save an experiment to your local library with publications and pipeline info. Required before compare or citations.' It names specific related tools (encode_compare_experiments, encode_get_citations, encode_export_data) and provides clear prerequisites, making it easy for an agent to choose this tool over alternatives like encode_get_experiment or encode_search_experiments.

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