get_statetree_states

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

No annotations are provided, so the description must disclose behavioral traits. It mentions the JSON tree output and the recursion behavior controlled by max_depth, but does not discuss side effects, performance implications, or read-only nature. The disclosure is adequate but not exhaustive.

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 well-structured with a concise overview, parameter usage explanation, and an Args section. It is appropriately sized for the complexity, though some might argue the Args section is slightly redundant. Overall efficient.

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 the presence of an output schema (not shown), the description need not detail return values. It adequately covers the tool's behavior and parameter usage. It is complete for a retrieval tool, though it could be enhanced with a brief note about permissions or performance.

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 description adds significant meaning beyond the input schema: it explains the purpose of asset_path (content path), max_depth (recursion control with specific values), and name_filter (case-insensitive substring match). The schema has 0% description coverage (meaning the schema itself lacks descriptions), so the description fully compensates.

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 'Get state hierarchy as a JSON tree' and specifies the contents (name, type, ID, task/transition counts). It distinguishes from sibling tools like get_statetree_state which likely returns a single state, by focusing on the hierarchical tree structure.

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 explains how to use max_depth and name_filter, providing clear examples (e.g., '0=roots only, 1=roots+children, -1=unlimited'). However, it does not explicitly state when not to use this tool or mention alternative tools for different needs, so it lacks explicit exclusions.

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