trinity_orchestrate

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

Discloses key behaviors: creates/updates local task records, may execute agent commands, returns evidence. Annotations already indicate readOnlyHint=false and openWorldHint=true, but description adds specific context about local records and commands, with no contradictions.

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?

Concise and front-loaded: first sentence defines core function, second gives usage guidance, third adds behavioral details. No unnecessary words.

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?

Covers purpose, usage, behavioral effects, and return value ('evidence'). Without an output schema, more detail on evidence format would be helpful, but given open-worldHint and complexity, it is adequate for agent selection and 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?

Schema coverage is 100%, so baseline is 3. The description adds extra context beyond schema descriptions, such as 'reserved for wait-aware clients' for wait/wait_timeout and 'agent id to avoid' for previous_agent, providing useful nuance.

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 clearly states the tool runs a multi-step Trinity workflow, distinguishes two modes (pipeline file or review flow), and explicitly contrasts with dispatch tools for single tasks. The verb 'orchestrate' aligns with the description.

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?

Provides explicit guidance: 'Use this for work that needs sequencing, review gates... use dispatch tools for a single agent task.' This clearly defines when and when not to use, with named alternatives.

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