Get Filter Values

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and idempotentHint=true. The description adds that it returns a JSON list, but does not provide additional behavioral details beyond what annotations convey. There is no contradiction, but the description adds limited transparency beyond 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 sections (purpose, when to use, related tools, args, returns). While slightly lengthy, every sentence adds value and the key information is front-loaded. Minor reduction could be possible, but overall concise for the coverage provided.

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 has only one parameter and an output schema (mentioned as JSON list), the description covers all essential aspects: purpose, usage context, all parameter options with examples, and return type. It is complete and leaves no ambiguity about how to use the 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?

With 0% schema description coverage, the description fully compensates by documenting each enum value with examples (e.g., 'assays: Available assay types (Histone ChIP-seq, ATAC-seq...)). This adds significant meaning beyond the schema's enum list, making parameters self-explanatory.

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 'Get available filter values for ENCODE searches' with a specific verb and resource. It distinguishes itself from sibling tools like encode_search_experiments by focusing on retrieving valid filter values rather than executing searches.

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 includes 'WHEN TO USE' and 'RELATED TOOLS' sections. It advises using this tool before searching to prevent typos and mentions alternative tools (encode_get_facets, encode_search_experiments), providing clear context for when to use this tool versus others.

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