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

Annotations already provide readOnlyHint, openWorldHint, and destructiveHint, so safety and mutability are covered. The description adds useful context about the source (Cosmik) and filtering capability, but does not disclose behavior like ordering, defaults beyond schema, or response format, making it adequate but not rich.

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 a single sentence that is front-loaded with the core purpose and includes all key details (source, article type, optional filter). Every word earns its place with no redundancy.

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?

Given the tool's simplicity, full schema coverage, and availability of an output schema, the description adequately covers the essential context: what is returned, source, and filtering option. There are no significant gaps for this straightforward listing tool.

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 100% for both parameters, so baseline is 3. The description adds semantic nuance by stating the search term filters by mission, rocket, or provider name, which complements the schema's examples (e.g., 'Starship') and clarifies the intent of the query parameter.

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?

Description clearly states the tool returns the latest rocket-launch news articles (previews and post-launch recaps) from Cosmik, with optional filtering. This distinguishes it from siblings like get_iss_passes and get_next_launches, which cover ISS passes and launch schedules.

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 implies usage for retrieving news articles, and the sibling names suggest alternatives, but it does not explicitly state when to use this tool over others or mention any exclusions. Guidance is implied rather than direct.

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