get_sigorta_tahkim_document_markdown

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

Annotations indicate readOnly and idempotent. Description adds key behaviors: returns paginated Markdown (not raw PDF), and scope of available issues (1-64, 2010-2025). No contradictions.

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 sentences, front-loaded with purpose, no redundant information. Each clause serves a clear function.

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 purpose, scope, output format, and pagination. Output schema exists, so return value details are not needed. Could mention page number behavior (default 1) but schema covers that. Missing minor guidance on iteration for full content.

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 covers both parameters with descriptions. The description adds minimal extra meaning (e.g., 'by number', 'paginated'), but baseline is 3 due to 100% schema 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?

The description clearly states the verb 'Retrieve' and the resource 'full PDF content of a Sigorta Tahkim Komisyonu Hakem Karar Dergisi issue by number'. It distinguishes from sibling tools like 'search_within_sigorta_tahkim_issue' by focusing on retrieving an entire issue.

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?

Implicitly indicates use to retrieve full issue content, but lacks explicit when-to-use or when-not-to-use guidance compared to sibling tools. No mention of alternatives like search tools.

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