tcai_convergence

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

No annotations provided, so description carries full burden. It explains the halting condition in detail, including the three criteria (free energy, task quality, epistemic value) and the patience cycles requirement. References external source for further details.

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?

Three sentences: purpose, read vs write mode, and halting condition. Efficient and well-structured, no wasted words.

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 no output schema, description indicates return of satisfaction state and active thresholds. Parameters are all optional and described. Complete for a read/write configuration tool.

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 covers all 5 parameters with descriptions. The tool description adds collective context by explaining how parameters relate to the halting condition, but does not individually elaborate beyond the schema.

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 inspects or configures the halting criterion, specifying that no arguments returns state and arguments update thresholds. This distinguishes it from sibling tools like tcai_cycle or tcai_workspace_state.

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?

Explicitly describes two usage modes: read (no arguments) and write (with arguments). Provides clear condition for each. However, lacks explicit guidance on when to use this over sibling tools like tcai_cycle or tcai_metrics.

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