Track automatic submissions

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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world, so the safety profile is covered. The description adds a real piece of behavioral context — the API key requirement — plus interpretation rules for submission/listing status, though it says nothing about error behavior when the ID is unknown or about the returned shape.

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 with the auth requirement front-loaded, so it is compact. However, the middle sentence is a dense, comma-spliced noun pile that is hard to parse, trading clarity for brevity.

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 one-parameter getter with no output schema, the description should convey what comes back and for which entity. It gestures at return content (evidence, waits, operator-attention states) but never ties the call to a launch ID or covers not-found behavior, leaving gaps an agent must guess at.

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% and the sole parameter `launch_id` is never mentioned in the description. The text talks around the data ('owned jobs') but does not tell the agent it must supply a specific launch UUID to scope the read, so the description fails to compensate for the schema gap.

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?

The description never states plainly that this retrieves a single launch by ID; instead it lists data categories ('Read owned jobs, real provider IDs, evidence, ingestion waits and operator-attention states'), which reads closer to a listing tool. With a sibling `list_launches` present and no differentiation, an agent could easily confuse the two.

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?

'Submitted is not approved; listed requires matching provider evidence' is domain guidance about launch status semantics, not about when to call this tool versus `get_launch_intake`, `get_preflight`, or `list_launches`. There are no conditions, prerequisites, or exclusions given for selecting this tool.

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