get_statutory_chain

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

No annotations provided; the description explains the walking behavior and max_depth constraint but omits details like read-only nature, side effects, or data source, leaving some behavioral gaps.

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 with zero wasted words, front-loading the purpose; highly concise and 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?

No output schema exists; the description explains the tree traversal and use case but lacks details on return format or structure, though it is mostly sufficient for an agent to understand the tool's purpose.

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 100% with descriptions for both parameters; the description adds minimal value beyond the schema (e.g., 'up to max_depth'), so baseline 3 is appropriate.

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 discovers the statutory chain for a Czech IČO, uses specific verbs ('Discover') and resource ('Czech IČO'), and distinguishes from siblings like get_dd_report and get_risk_score.

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 notes it is 'Useful for KYC and shell-company unwinding' but does not explicitly state when to use vs. alternatives or when not to use, making usage guidance implicit.

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