import_life_list

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

With no annotations, the description carries full responsibility for disclosing side effects. It only says 'Import' without revealing whether the operation replaces or merges the existing life list, requires authentication, or affects other data. This is a significant gap for a mutation tool, mirroring the deficiencies seen in the update_drive calibration example.

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 two sentences, front-loaded with the main purpose, and includes only essential information (source URL and input methods). No unnecessary words or repetition.

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?

The description covers the data source and input options, partially leveraging the rich schema. However, it omits behavioral expectations such as what happens post-import, success/failure reporting, and the implicit constraint that exactly one of the two parameters should be provided. For a tool with no output schema and no annotations, this is adequate but incomplete.

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 already provides detailed descriptions for both parameters (csvPath and csvContent) including mode labels. The description's 'Provide either a file path or paste the CSV content directly' reinforces the either/or relationship but adds no new semantic value beyond what the schema states.

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 action ('Import your eBird life list') with the specific source ('CSV export'). Including the URL for obtaining the file further clarifies the exact resource. This distinguishes the tool from sibling read-only tools like check_life_list or get_life_list_stats.

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 clear context: use when you have an eBird life list CSV, with explicit instructions to download from ebird.org/downloadMyData. It also explains the two input modes (file path vs. pasted content). However, it does not explicitly mention alternatives or when not to use it, though the uniqueness among siblings makes this less critical.

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