get_teblig_content

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

No annotations are provided, so the description carries full burden. It states the tool returns Markdown content and is ready for analysis, implying read-only behavior, but does not explicitly mention no side effects or any authentication/rate limits. A simple fetch tool, but could be more explicit.

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 concise (3 sentences plus example) and front-loaded with the purpose. Every sentence adds value, and the example usage clarifies the workflow. No unnecessary text.

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?

The tool has an output schema (though not detailed), so the description need not explain return format. It mentions Markdown and readiness for analysis. Given the simple retrieval nature and sibling context, it is fairly complete, though error handling or availability info is missing.

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%, so baseline is 3. The description's parameter guidance ('The communiqué number from search results (e.g., '42331')') mirrors the schema descriptions exactly, adding no new semantic value beyond what the schema already 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 full content of a Turkish communiqué in Markdown format, with a specific verb ('Retrieve') and resource ('Turkish communiqué (Tebliğ)'). It distinguishes itself from sibling tools that handle other document types (e.g., get_cbgenelge_content, get_mevzuat_content) or search functions.

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 description explicitly advises to use 'search_teblig' first to find the communiqué number and series, providing a clear usage workflow (search then get content). It does not list exclusions or when not to use, but the context is clear given siblings.

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