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

The description explicitly discloses that the prompt is discarded and that a fixed template is returned, which is a key behavioral trait beyond any annotations. This transparency helps the agent avoid expecting prompt-dependent behavior, though it does not describe the template's content.

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 two short sentences with zero waste. The primary purpose is front-loaded, and the behavioral caveat follows immediately.

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?

For a tool that returns a static template and ignores inputs, the description is sufficient. It does not explain the template's steps, but the name 'think-steps' and the phrase 'three-step thinking template' provide enough context for an agent to understand the tool's role.

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 schema already documents each parameter as discarded after a shape check, so the description adds little new parameter meaning. The statement 'Prompt discarded' reinforces the schema but does not expand on parameter usage.

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 returns a three-step thinking template, which is a specific output. The phrase 'Prompt discarded' clarifies that it does not process the prompt, distinguishing it from sibling tools that perform checks or transformations.

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 guidance is given on when to use this tool versus alternatives. It does not mention scenarios or prerequisites, leaving the agent to infer that it is a simple template-returning utility.

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