JARVIS

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

With no annotations provided, the description carries full burden for behavioral disclosure. It mentions key behaviors like single-tool-per-iteration enforcement and fractal decomposition, but omits details on error handling, state persistence, or what happens when invalid phase_completed values are provided. The behavioral coverage is adequate but incomplete.

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 informative and structured with a clear opening sentence followed by a bullet-like list of features. However, it contains some redundant phrasing (e.g., 'Enables Claude to autonomously manage complex projects through context segmentation') that could be trimmed without loss of clarity.

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 and moderate complexity, the description covers the phase loop and key features but lacks details on expected return values, state transition rules, and post-execution behavior. It is adequate for basic usage but leaves gaps for an agent needing precise 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 description coverage is 100%, so baseline is 3. The description does not add significant meaning beyond the schema's parameter descriptions; it merely reiterates the phase completion semantics and session handling. No additional value for parameter understanding.

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 identifies the tool as a 'Finite State Machine Controller' implementing an 8-phase agent loop, with a specific verb ('implements') and resource ('8-phase agent loop'). It distinguishes itself from siblings by detailing unique features like fractal task decomposition and single-tool-per-iteration enforcement.

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?

The description does not provide any guidance on when to use this tool versus its siblings (e.g., APITaskAgent, IronManusStateGraph). It lacks explicit 'when to use' or 'when not to use' criteria, leaving the agent to infer applicability from the feature list alone.

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