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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds substantive behavior beyond that: exactly which metadata fields come back and the important constraint that no full text is returned, only a link. It does not cover failure behavior for an invalid address, hence not a 5.

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?

Three short sentences, front-loaded with the returned content, then the input, then the delimiting constraint. No filler, though the sentence structure is somewhat list-like rather than prose.

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?

For a single-parameter read tool with rich annotations and no output schema, the description covers return contents, input forms, and the full-text limitation – which is what an agent needs. Only minor gaps remain, such as what happens with an unresolvable or unknown slug.

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% and the single parameter already documents that a full URL or a slug is accepted, so the schema carries the load. The description restates the same dual-input acceptance without adding format edge cases, normalization rules, or ambiguity resolution between URL and slug – baseline 3 for full 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?

Description opens with a specific verb-and-resource statement ("Bir Ortak Alan yazısının başlığı, konusu, yazarı, tarihi ve kısa özeti") and enumerates exactly which fields are returned, so an agent knows it is a per-article summary lookup. It never names sibling tools such as yazi_ara or son_yazilar, so differentiation from them is left to inference.

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?

Usage is implied by "Girdi: yazının adresi ya da adresteki kısa ad (slug)" – call it when you have an article address. The note "Tam metin verilmez; bağlantı paylaşılır" usefully signals when this tool is NOT enough (full-text retrieval), but no alternative tool or explicit when-not condition is named.

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