get_mevzuat_madde_tree

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

No annotations provided, but description fully explains the hierarchical return structure and mentions the source domain. It does not disclose any potential side effects or rate limits, but for a read operation with no destructive actions, this is adequate.

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 bullet points and a clear workflow. Every sentence adds value—no fluff. It is front-loaded with the main purpose and efficiently conveys all necessary information.

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 complexity of Turkish legislation and the number of sibling tools, this description is complete. It explains the return structure (with output schema present), provides compatibility notes, and offers a workflow. No gaps remain for an AI agent to understand how and when to use this 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?

The single parameter mevzuat_id is fully documented in the input schema, and the description adds critical workflow context: that it must come from search_mevzuat results, is a string ID not a law number, and provides an example. This goes beyond what the schema alone provides.

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 retrieves the article tree (table of contents) of Turkish legislation from a specific source. It distinguishes itself from siblings by listing compatible legislation types and noting tools that return empty, providing clear differentiation.

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?

Explicit guidance on when to use (with specific legislation types like KANUN, CB_KARARNAME) and when not to (CB_KARAR, CB_GENELGE, TEBLIGLER). Provides a workflow: search_mevzuat → get mevzuatId → use this tool, and suggests it as a precursor to other tools like search_within_mevzuat or get_mevzuat_content.

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