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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered by structured data. The description adds only that the cards are current and derive from the 'Rasadi insight engine', which is modest context beyond the annotations. It does not disclose ordering, freshness window, or volume of cards returned.

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?

A single short sentence with no filler, and the resource is front-loaded. It is efficient, though the extreme brevity borders on under-specification for a tool with an output schema worth orienting the agent toward.

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?

An output schema exists, so return values need not be explained, and annotations carry the safety profile. Still, for a tool whose purpose is to surface 'insight cards', the description leaves the agent without enough grounding to choose it over the sibling summary/link 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% and both parameters (site, api_token) are fully documented in the schema, including the fallback-to-first-site behavior and the OAuth alternative for the token. The description adds no parameter-level meaning beyond that, so the baseline of 3 applies.

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 names a specific resource ('guncel oneri kartlari' – current suggestion cards) and attributes it to the Rasadi insight engine, so the agent knows roughly what is returned. However, it never differentiates from siblings like gunluk_ozet (daily summary) or kirik_linkler (broken links), and 'oneri kartlari' is essentially a restatement of the tool name 'oneriler'. Vague but not tautological.

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?

No indication of when to call this tool versus gunluk_ozet, kirik_linkler, or siteler, and no prerequisites or exclusions are stated. The agent must infer usage entirely from the tool name and the noun phrase in the description.

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