Get Mevzuat Madde Tree

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds only that the output is a table of contents/article tree — effectively restating the title — and since an output schema exists, even that is not new information.

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?

It is a bare noun-phrase label rather than a description; brevity here comes from under-specification, not efficiency. As with a one-word description, the fragment does not carry enough information to earn a higher score.

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?

An output schema means return values need not be explained, and the single parameter is fully covered by the schema. What is missing for a tool in a crowded mevzuat family (search_mevzuat, get_mevzuat_content, search_within_mevzuat, get_mevzuat_gerekce) is any routing guidance, leaving an agent unable to choose correctly.

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?

There is a single parameter with 100% schema description coverage ('search_mevzuat sonucu mevzuat_id'), so the schema fully documents it. Per the rubric, high coverage with no extra description detail lands at the baseline of 3.

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 phrase names the resource and the shape of the result ('içindekiler / madde ağacı'), so an agent knows it returns a hierarchical TOC of a mevzuat. However there is no verb and no differentiation from siblings such as get_mevzuat_content or search_within_mevzuat, which also operate on mevzuat content.

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?

No when-to-use guidance is given. The description never says to call this before or instead of get_mevzuat_content, nor what condition (e.g., needing document structure vs full text) should select this tool.

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