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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), so the bar is lower. The description still adds output-shape context absent from any output schema: entries carry a `url` and may have a `see` page, and the tool returns grouped content meant to be answered from directly.

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-loaded with the topical coverage that identifies the tool, then the usage instruction and parameter note. Two dense sentences with little waste, though the long enumeration of topics is slightly run-on.

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 single optional-enum, read-only tool with no output schema, the description says enough: what it covers, when to call it, how to use the result, and how to filter. Only the exact return structure is left implicit, which is acceptable for a documentation lookup.

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 100% and the enum documents all seven values, so the schema already carries the parameter meaning. The description restates the behavior ('pass topic to read one group; leave it out for all of them') but adds no syntax or semantics beyond the schema; baseline 3 is appropriate.

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 (returns FAQ answers about the SPACEXPLORATION platform itself) and enumerates the topical scope: pricing, listing, leads, finding, AI assistants, building data, accounts. This clearly distinguishes it from the many listing/parcel siblings, which operate on user data rather than platform documentation.

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 an explicit trigger ('Call this before answering any question about how SPACEXPLORATION works or what it costs') plus post-call behavior ('answer from what it returns', link the url/see page). Strong when-to-use guidance, though it names no explicit when-not condition or alternative tool.

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