get_mevzuat_content

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

With no annotations, description discloses return format (plain text, stripped HTML), warns about large documents, and outlines correct ID usage. Could mention network dependency but is overall transparent.

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?

Every sentence earns its place: purpose, format, warning, workflow, and instructions. Well-structured with no redundancy.

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?

Covers all key aspects: input, output format, warnings, workflow, and alternative tool usage. Complete for a tool with output schema.

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%, and description adds value by specifying ID format, giving an example, and clarifying it is not a law number. Exceeds baseline for high coverage.

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?

Clearly states it retrieves full content of Turkish legislation, specifies source and output format, and distinguishes from siblings by referencing mevzuatId from search_mevzuat and warning about large documents.

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?

Provides explicit workflow, warns when to use search_within_mevzuat instead for large documents, and clarifies that mevzuatId comes from search_mevzuat, not law numbers.

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