orchestration

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

The description claims the tool can enable or disable, which are write operations, but annotations include readOnlyHint: true. This is a direct contradiction. The description does not disclose any other behavioral traits.

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?

Two sentences, zero wasted words. First sentence clearly states purpose, second provides usage context linking to sibling tool.

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?

Tool has 2 parameters and no output schema; description covers action values but fails to explain return behavior or reconcile the annotation contradiction, leaving incomplete picture.

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. Description adds value by listing action values 'enable | disable | status' but does not elaborate on repo beyond its schema description.

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 enables, disables, or checks local orchestration, specifying verbs and resource. It distinguishes from sibling 'orchestrate' by mentioning it is for guided investigation workflows.

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?

Description explicitly tells when to use this tool (to manage orchestration state) and when to use 'orchestrate' (for workflows). It does not mention when not to use or other alternatives, but provides clear context.

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