Chain-of-Thought Reasoning

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint:false, so the agent knows it's safe and side-effect free. The description adds that reasoning is 'structured' and involves decomposition and exploration, which provides some behavioral context but doesn't disclose return values or internal processes. No contradiction with annotations.

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 concise sentence that front-loads the core purpose and lists key actions. It avoids filler and is appropriately sized for a simple internal-reasoning tool, but it could include a bit more detail without becoming verbose.

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?

There is no output schema, and the description does not clarify what the agent receives after calling the tool (e.g., a reasoning summary or just an acknowledgment). The roles of the steps and context parameters are also left ambiguous. For a tool that assists reasoning, this lack of return and parameter context is a significant gap.

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%, and the description does not explain any of the three parameters (problem, steps, context). While names and types are somewhat self-explanatory, the description adds nothing about how steps or context influence the reasoning process. With zero coverage, the description should compensate, but it does not.

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 performs structured chain-of-thought reasoning and lists specific actions (decompose, explore, conclude). It implicitly distinguishes from sibling analysis tools that run concrete checks (e.g., security_scan, code_quality) by focusing on internal reasoning. However, it doesn't specify the output or how it assists, leaving a slight ambiguity.

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 explicit guidance is given on when to use this tool versus the many sibling tools. It does not mention that it should be used for logical reasoning before invoking analysis tools, nor does it provide any exclusion criteria or alternatives. Given the large toolset, this is a notable gap.

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