encode-toolkit

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

Annotations already indicate this is a read-only, non-destructive, idempotent operation with a closed-world scope. The description adds valuable context beyond annotations by specifying the prerequisite that 'Both experiments must be tracked first' and detailing what aspects are compared, which helps the agent understand behavioral constraints not covered by annotations.

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 with distinct sections (purpose, comparison details, prerequisites, usage guidelines, related tools, args, returns), each sentence adds value without redundancy, and key information is front-loaded. It efficiently conveys necessary information in a compact format.

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 (compatibility analysis), the description is complete: it explains the purpose, usage context, prerequisites, parameters, and return format. With annotations covering safety and an output schema detailing the JSON report, the description provides all necessary contextual information without needing to repeat structured data.

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?

With 0% schema description coverage, the description fully compensates by clearly explaining both parameters (accession1 and accession2) with examples ('ENCSR133RZO', 'ENCSR000AKS') and their roles ('First experiment accession', 'Second experiment accession'). It adds essential meaning beyond the bare schema, though it doesn't elaborate on format constraints beyond 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 the tool's purpose with specific verbs ('analyze', 'compares') and resources ('two ENCODE experiments'), and distinguishes it from siblings by focusing on compatibility assessment rather than tracking, downloading, or searching. It explicitly mentions what aspects are compared (organism, genome assembly, assay type, etc.).

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 includes an explicit 'WHEN TO USE' section that specifies the exact scenario ('check if two experiments are compatible for combined analysis') and prerequisites ('Both must be tracked first'). It also lists related tools (encode_track_experiment, encode_list_tracked) to guide alternatives, providing comprehensive usage guidance.

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