Export Tracked Data

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

Annotations already mark the tool as read-only, non-destructive, and idempotent. The description adds that the output includes specific fields, filters support partial matching, and that generated PMIDs are usable with PubMed MCP tools. However, it does not disclose potential export limits or pagination 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 with sections for purpose, content details, usage context, related tools, parameters, and returns. Every sentence serves a purpose, and the most important information (what it exports and format options) appears first.

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 an output schema, the description adequately explains what the tool does, its parameters, and how results can be used. It covers filtering, format variants, and integration with other tools, making it sufficiently complete for an agent to understand and invoke correctly.

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?

The schema provides 4 parameters with no descriptions (0% coverage). The description compensates by explaining format options with use cases (csv for Excel, tsv for R/pandas, json for programmatic use) and clarifying that filter parameters use partial matching. This adds meaningful context beyond the raw 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 'Export tracked experiments as a table (CSV, TSV, or JSON)' and lists included metadata, publication counts, PMIDs, and derived file counts. It distinguishes from related tools like encode_list_tracked and encode_summarize_collection.

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 a 'WHEN TO USE' section ('Use to create shareable tables... for manuscripts and reports') and lists related tools. It explains the output's utility with PubMed MCP tools, but does not explicitly state when not to use or provide alternative selection criteria.

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