begin_thought

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

Discloses failure condition when thought in progress, which is a behavioral trait. No annotations exist, so description carries the burden. Could be more specific about what 'draft' entails (e.g., saves to session, editable).

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?

Two sentences; first states purpose, second adds condition and parameter format. No fluff, but could be more concise.

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?

Has output schema so return values are covered. Description provides key usage points but lacks guidance on when to use among many sibling tools and deeper behavioral 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?

Schema coverage is 0%, but description adds format details for tags and axioms (JSON array or comma/newline list). Does not explain content or session_id parameters.

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?

Clear verb+resource ('Draft a new thought') with context ('in the session's current stage'). Differentiates from siblings like commit_thought and critique_current_thought.

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 warns against use if thought in progress, providing a precondition. Does not explicitly compare to alternative tools, but the condition is useful.

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