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

With no annotations provided, the description carries the full burden of disclosing behavioral traits, but it does not. It mentions 'composite' and 'full result', which hint at a multi-step operation, but it does not explain side effects, async behavior, potential costs, or output structure. The schema includes an 'async' flag, but the description never acknowledges it.

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 extremely short, but this is under-specification rather than effective conciseness. The phrasing 'goal in, full result out' is stylized and wastes the limited space on a gimmick instead of conveying essential information. A single well-constructed sentence could have explained the tool's purpose and key parameters.

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 that the tool has three parameters, no output schema, and no annotations, the description is severely inadequate. An agent would not know what a 'mission' entails, what to provide in 'template', or what the returned result looks like. The context is entirely missing, making this tool effectively unusable from the description alone.

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%, yet the description only hints at 'goal' and completely ignores 'async' and 'template'. It does not explain the meaning of 'goal', whether 'template' refers to a mission template, or what 'async' controls. Since there are no parameter descriptions in the schema, the tool description was the only opportunity to compensate, and it fails almost entirely.

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 'Composite mission — goal in, full result out' is a cryptic fragment, not a clear statement of what the tool does. It lacks a specific verb and resource, and it does not distinguish this tool from siblings like run_chain or plan. The phrase 'composite mission' is ambiguous, and the input-output framing is more of a tagline than an explanation.

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?

No guidance is provided on when to use this tool versus alternatives. The description does not mention any specific use case, prerequisites, or exclusions. It only vaguely implies that a 'goal' is needed, but this is generic and does not help an agent decide between run_mission and other high-level orchestration tools.

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