agora_list_missions

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

No annotations are provided, so the description carries the full behavioral burden. It implies a read operation through 'List' and hints at 'untrusted remote content', but does not disclose auth requirements, pagination behavior, rate limits, or how to handle untrusted results.

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 front-loaded sentence and avoids unnecessary text. The parenthetical '(untrusted remote content)' is concise but somewhat vague and could use clearer integration.

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?

The tool is simple with one optional parameter and an output schema exists, so the description need not explain return values. However, without annotations or parameter documentation, it leaves gaps around state values, pagination, and permission context for an agent to call it confidently.

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 schema does not explain the single 'state' parameter beyond its type and default null. The description says it is an optional filter by state but adds no allowed values, format, or meaning for valid state inputs, leaving the parameter semantics largely undocumented.

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 states a specific verb (List) and resource (Missions), and adds an optional filter by state. It distinguishes the tool from sibling get_mission by being a list operation, though it does not explicitly name alternatives or scope boundaries.

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 only says the tool lists Missions with an optional state filter. It gives no guidance on when to use this versus list_debates, get_mission, list_mission_tasks, or other listing tools, and no prerequisites or when-not conditions.

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