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

Goes beyond the annotations by disclosing access conditions: no login, no VIP membership, no submission quota required. Annotations cover the mutation profile (readOnlyHint=false, destructiveHint=false, idempotentHint=false), but the description still omits what happens after submission (immediate ack vs. human follow-up) and that repeat calls create duplicate requests.

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?

Three short sentences, each earning its place: purpose first, then access prerequisites, then content requirements. No filler or restatement of the title.

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?

For a four-parameter, no-output-schema submission tool this covers purpose, prerequisites and what to put in the body. The remaining gap is post-submission behavior and the meaning of the two contact-related fields, which an agent would otherwise have to guess.

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 description coverage is 0%, so the description must carry the load. It explains 'what data is needed' (request) and 'how the Agent would use it' (useCase), but never mentions contact or agentName, leaving half the parameters undocumented anywhere.

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 and resource: 'Submit any unmet data need directly to the eoidata product team.' This instantly separates it from every sibling, which are all read-only retrieval tools (get_*, search_*, compare_*), since this is the only outbound submission tool in the set.

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 phrase 'any unmet data need' implicitly defines the trigger condition: use it when the catalog and existing retrieval tools cannot answer the question. It does not explicitly name a fallback path (e.g. 'check get_data_catalog first'), so it stops short of full when/when-not guidance.

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