debug_workflow

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

With no annotations provided, the description bears full responsibility for disclosing behavioral traits. It indicates the tool is analytical ('analyze', 'provide debugging insights'), implying a read-only operation, but does not confirm lack of side effects, required permissions, rate limits, or output format. The minimal disclosure leaves significant ambiguity about its behavior.

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 sentence that immediately conveys the tool's purpose without any extraneous words. It is front-loaded and efficient, earning its place with no waste.

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 the tool has no output schema and no annotations, the description should compensate by explaining what the debugging insights include (e.g., error logs, step traces) or any other behavioral details. The current description is too brief to cover the tool's complexity, leaving users uninformed about the results and operational context.

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 input schema has 100% description coverage, so both parameters (workflow_id, error_context) are already documented. The description does not add any parameter-specific meaning beyond what the schema provides. Per guidelines, baseline 3 is appropriate since schema handles the burden.

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's purpose: 'Analyze workflow execution results and provide debugging insights'. It specifies a verb ('analyze') and a resource ('workflow execution results'), making the core function understandable. However, it does not explicitly distinguish this tool from its siblings (analyze_bioinformatics_task, execute_claude_script), though the names imply different domains.

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 guidance on when to use this tool versus alternatives, no prerequisites, and no exclusion criteria. It simply states what the tool does without context for decision-making, leaving the agent without direction on when this tool is appropriate.

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