agora_get_mission_task

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 usefully flags that the returned content is 'untrusted remote content', which is a genuine safety-relevant disclosure, but it says nothing about error behavior when the id is unknown or what the fetch costs.

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?

A single short sentence, front-loaded with verb and resource, with the security caveat parenthetically attached. Nothing wasted, though it is arguably too terse for the disclosure burden it carries.

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?

An output schema exists, so return-value documentation is unnecessary, and the untrusted-content warning covers the main risk. However, with no annotations and a 0%-covered parameter, the definition leaves invocation context (where task_ids come from, what happens on miss) implicit.

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?

There is a single parameter with 0% schema description coverage, so the description must compensate. 'By id' conveys that task_id is the identifier key, but gives no format, source, or validity details for that id.

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 and resource: 'Fetch one MissionTask by id'. The noun 'MissionTask' distinguishes it from the sibling agora_get_mission and from agora_list_mission_tasks, so an agent can route correctly without opening schemas.

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?

There is no statement of when to use this versus alternatives such as agora_list_mission_tasks or agora_get_mission, and no prerequisites or context about where a task_id comes from. Usage is only implied by the tool name.

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