Get Mevzuat Content

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 that the output is paginated Markdown, which is useful behavioral context. However, it says nothing about pagination limits around the edges (e.g., behavior past the last page) or response size beyond the schema-implied 5000-char page.

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, front-loaded sentences with zero filler. The essential identity (full text by id) and the key constraint (not the law number) are stated immediately.

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 described, and annotations cover safety. Combined with full schema coverage, the description is sufficient for correct invocation, though the pagination behavior could be marginally more explicit for a paginated full-text 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?

Schema description coverage is 100%, so the schema already documents both params (page = 5000-char page, mevzuat_id from search). The description adds real value beyond that by emphasizing the id must originate from search_mevzuat and explicitly warning it is not the law number (kanun numarası), a genuinely useful disambiguation.

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 a specific verb+resource: retrieve the full text content of a mevzuat identified by mevzuat_id, delivered as paginated Markdown. It clarifies the id's provenance (comes from search_mevzuat) and disambiguates from using a law number. It does not, however, explicitly differentiate against close siblings like get_mevzuat_madde_tree, get_mevzuat_gerekce, or search_within_mevzuat.

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?

Implies the correct workflow by noting the id comes from search_mevzuat, which tells the agent to search first. The 'not the law number' caveat prevents a common misuse. But there is no explicit when-to-use vs alternatives among the many get_/search_ mevzuat siblings, and no exclusions stated.

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