encode-toolkit

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

The description adds valuable behavioral context beyond annotations: it explains where credentials are stored (OS keyring securely), that they're never in plaintext, and the three specific actions available. While annotations provide hints (destructive, idempotent), the description elaborates on security implications and action semantics, though it doesn't mention rate limits or detailed error behavior.

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: it starts with the core purpose, then provides security context, usage guidelines, and parameter details. Every sentence adds value with no redundancy. The bullet-point formatting for parameters 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 (credential management with destructive operations), the description provides complete context: purpose, security implementation, usage boundaries, parameter details, and mentions the JSON return format. With annotations covering safety hints and an output schema existing, the description focuses on the semantic gaps effectively.

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 explaining all three parameters: 'action' with its three enum values and what each does, plus 'access_key' and 'secret_key' with their conditional requirements ('only for action="store"'). This provides complete parameter semantics beyond the bare schema.

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: managing ENCODE API credentials for accessing restricted/unreleased data. It specifies the verb 'manage' and resource 'credentials', and distinguishes from sibling tools by focusing on authentication management rather than data operations like search or download.

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 provides explicit guidance: 'WHEN TO USE: Use only for accessing unreleased/restricted ENCODE data. Public data requires no authentication.' It also names a related tool (encode_search_experiments) and clearly defines when NOT to use this tool, offering complete usage context.

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