get_uyusmazlik_document_markdown_from_url

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

Annotations already declare readOnlyHint=true and idempotentHint=true, so the agent knows this is a safe, repeatable read operation. The description adds value by specifying the output format ('clean Markdown format'), which isn't covered by annotations. However, it doesn't provide additional behavioral context like rate limits, authentication needs, or error conditions.

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 extremely concise with just two sentences that are front-loaded and waste-free. Every word contributes essential information about purpose and output format without any redundancy or fluff.

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?

Given the tool has annotations covering safety (readOnlyHint, idempotentHint), 100% schema coverage, and an output schema exists, the description provides adequate context. It specifies the court type and output format, which complements the structured data well. However, it could be more complete by mentioning it's specifically for documents from search results (as hinted in the schema) to better integrate with sibling tools.

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%, with the single parameter 'document_url' well-described in the schema. The description doesn't add any parameter-specific information beyond what's in the schema, so it meets the baseline of 3 where the schema does the heavy lifting.

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 ('retrieving') and resource ('full text of an Uyuşmazlık Mahkemesi decision'), and specifies the output format ('clean Markdown format'). It distinguishes from some siblings by focusing on this specific court, but doesn't explicitly differentiate from other document retrieval tools like 'get_anayasa_document_unified' or 'get_bddk_document_markdown' beyond the court name.

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 provides some usage context with 'Use this when retrieving full text of an Uyuşmazlık Mahkemesi decision,' which implies this tool is for decisions from that specific court. However, it doesn't explicitly state when NOT to use it or mention alternatives among the many sibling search and retrieval tools, leaving some ambiguity about tool selection.

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