Get Mevzuat Gerekce

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 nothing beyond that: it never mentions the pagination behavior implied by the 'page' parameter, result size, or what the gerekçe payload contains, leaving the behavioral burden unmet.

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 short sentences with the resource named first and the prerequisite second; nothing is padded. It is efficient, though arguably terse to the point of under-specification rather than genuinely concise.

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 exists, so return values need not be explained, but the tool still leaves the undocumented 'page' parameter and the lack of differentiation from sibling mevzuat getters unaddressed. For a lookup tool in a family of near-identical get_* tools, that is a meaningful shortfall.

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 only 50%: 'gerekce_id' is documented in the schema (and merely restated in the description), while 'page' has no description anywhere. The description does not compensate for that gap, so it adds no meaning beyond the structured fields.

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?

States the specific resource ('Kanun gerekçesi') and names the prerequisite input, making the purpose recoverable without opening the schema. It does not, however, distinguish itself from sibling lookups such as get_mevzuat_content or get_mevzuat_madde_tree, so an agent must infer which mevzuat sub-resource this returns.

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 sentence 'search_mevzuat sonucundaki gerekce_id gerekir' implies the intended workflow (search first, then fetch by id), which is genuine usage context. There is no explicit when-to-use vs when-not guidance and no mention of the alternatives among the get_mevzuat_* siblings.

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