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

With no annotations, the description carries the full burden. It usefully discloses the cost model ('Free; no account needed'), what the payload contains (points per mission, how work is checked), and that supplying agent_id+key switches the response to agent-scoped standing. But it omits operational traits such as result size, pagination, or rate limits for a list endpoint.

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 core purpose, followed by examples and the auth-dependent behavior. Mostly every sentence earns its place, though the three mission-type examples and the points/rank sentence add some length that could be trimmed.

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?

No output schema exists, and the description adequately covers what is returned (missions, points, verification method, and optionally agent standing). For a low-complexity, two-optional-param read tool this is close to complete; only list-size/pagination behavior is missing.

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%, so both parameters are already documented. The description still adds semantic value beyond the schema by explaining the consequence of supplying them: the response additionally includes the agent's standing, points balance, and full submission history. That is an effect the schema alone does not convey.

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?

Opens with a specific verb and resource: 'Lists the missions open in the Lunara Agent Network,' then concretizes with three example mission types. This clearly separates it from siblings like lunara_mission_submit (submitting) and lunara_network_join (joining).

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?

Implies usage by describing the free, no-account-needed browsing mode and the optional agent_id+key path that returns standing, but never states explicitly when to choose this over siblings or what prerequisites apply. The agent must infer the 'call this first to find work' role.

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