Read a local BADM (BIF) file

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

Annotations already cover safety (readOnly, idempotent, non-destructive, closed-world), so the description's real contributions are the privacy behavior ('Emails and addresses are withheld by default'), the archive-unwrapping capability ('also from inside the zip'), and the transport constraint ('stdio only'). Those are genuinely additive traits not derivable from the structured fields.

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?

Front-loads verb and resource, and every clause adds information about contents or behavior with no filler. The middle is a single dense run-on enumeration with awkward fragments ('also from inside the zip'), which slightly hurts scannability but costs no wasted text.

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?

An output schema exists, so return values need not be described, and the safety profile is carried by annotations. The remaining gap is input disambiguation: with 7 optional parameters and neither `file` nor `site` required, the description never says which selector wins or what the default behavior is when none is supplied.

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?

Schema coverage is 71%, so the schema already documents most parameters; the description adds only loose mapping (groups -> 'entries by group (location, IGBP, team, instruments, disturbance …)', include_contacts -> withheld emails/addresses). It says nothing about pagination via `limit`/`offset` or about the bulk-file `site_id` filter, both of which carry no description in the 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?

Names a specific verb ('Read') and a specific resource (a local BADM Interchange Format file), then enumerates the payload (groups, UTC offsets, DOI/citation, funding) so the agent knows what comes back. It does not explicitly contrast with the sibling amf_get_badm, which likely serves the same content from a remote source, leaving the local-vs-remote distinction to be inferred.

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?

Gives a routing pointer ('Next: call amf_get_citation for the current citation') and clarifies the input shapes (BASE-BADM xlsx, FLUXNET CSV, or inside the zip), which implies when to reach for it. However, there is no explicit statement of when NOT to use it versus amf_get_badm or amf_list_files, and no guidance on what happens when both `file` and `site` are omitted.

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