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

No annotations, so the description carries full behavioral burden. It usefully explains the returned structure and confirms a read-only discovery character, but says nothing about ranking, matching behavior, or how broad a 'query' should be. A solid but not rich disclosure for a no-annotation tool.

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?

Opens with the core purpose sentence, then a clean field glossary. Well front-loaded, though the field list duplicates what an output schema already encodes, so a small amount is non-essential.

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?

Since an output schema exists, the description needn't explain return values, yet it helpfully glosses key fields to interpret them. Combined with the sibling routing note, it is nearly complete; only the vague query/fields semantics leave an agent with a minor open question.

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 40%: limit and cursor are well-documented in the schema, but query, fields, and scheme have no schema descriptions. The description covers query indirectly via the 'exact preferred labels' framing and names scheme values (sciencekeywords, platforms), partially compensating, yet fields and query syntax remain unexplained.

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?

States a specific verb+resource ('Discover official Earthdata vocabulary... from NASA's Keyword Management System'), names the exact system behind it, and explicitly distinguishes its role relative to a sibling ('to construct successful get_collections 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?

Gives clear intended context (finding exact preferred labels before searching) and points to the related get_collections search. Contains no explicit when-not-to-use framing or query-scoping caveats that belong to this workflow.

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