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

With no annotations, the description carries the transparency burden. It does disclose that the prompt is discarded, but it does not clarify side effects, return format, or failure 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 brief and free of fluff, front-loading the core action. The cryptic 'Prompt discarded' sentence costs a point but does not add unnecessary length.

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?

The tool is simple, but the description omits what the template contains, how it should be used, and why the nine parameters are present. With no output schema or behavioral details, an agent would likely need clarification before calling it.

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?

Although every parameter has a schema description, those descriptions mostly say the value is discarded or checked and then ignored, which does not explain how any parameter contributes to the tool's purpose. High schema coverage is offset by the fact that the parameters appear to be unrelated placeholders.

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 names a specific verb and deliverable: 'Return a three-step thinking template.' It distinguishes the tool from the sibling tools, though 'Prompt discarded' adds a little ambiguity about what input, if any, should be supplied.

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 call this tool versus any sibling, and 'Prompt discarded' is not enough to explain how to invoke it. The unusually broad set of optional parameters is also not tied to a concrete usage scenario.

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