md_task_submit

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It mentions 'preflight' and 'asynchronously submit,' but does not explain side effects, permissions, confirmation token requirements, or what happens if preflight fails. This is minimal behavioral context for a tool that likely triggers operations.

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 with no wasted words. It is appropriately concise for a high-level overview, though it sacrifices necessary detail 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?

Despite the presence of an output schema and 4 parameters, the one-line description leaves critical gaps: what does 'governed operation' mean, how does dry_run work, when is confirmation_token required, and how does asynchronous submission behave? The description is inadequate for correct tool invocation.

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?

The description does not reference any of the four parameters (tool_name, parameters, dry_run, confirmation_token). With 0% schema description coverage, the description should compensate by clarifying how these parameters are used, but it provides no such information.

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 'Preflight and asynchronously submit one exact governed operation,' which clearly identifies the action (submit) and resource (one exact governed operation). It distinguishes from sibling tools like md_task_query, md_task_cancel, and md_task_retry by emphasizing submission rather than status, cancellation, or retry.

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 provides no explicit guidance on when to use this tool versus alternatives. It does not mention prerequisites, exclusions, or scenarios where query/cancel/retry would be more appropriate. The 'preflight' aspect implies a validation step but lacks concrete usage context.

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