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

Annotations already declare readOnlyHint=true and openWorldHint=false, and the description adds genuinely new operational context: an authentication requirement with two credential forms (X-API-Key or Authorization: Bearer). It also discloses relevance ranking, which tells the agent results are ordered. It does not mention pagination or how limit interacts with ranking, but the auth disclosure is real value beyond the annotations.

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, no waste, with the core capability front-loaded and the auth prerequisite appended compactly in parentheses. Nothing could be removed without losing information.

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 tool with three undocumented parameters, a domain enum, no output schema, and a large sibling set, the description is too thin. An agent still cannot tell what values 'vertical' accepts, how large a default result set is, or when to prefer this over the news/events 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 0%, so all three parameters rest entirely on the description, which says nothing about 'query', 'limit' (1-50), or the 'vertical' enum (crypto/finance/tech/turkish). The word 'article corpus' loosely implies content scope but never explains that vertical narrows the corpus or that limit caps results.

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?

States a specific verb and resource: 'Full-text search over the article corpus with relevance ranking.' An agent can distinguish it from aggregate siblings like muhabbit_sentiment_index or muhabbit_ticker_summary, but the description never names the closest alternative (muhabbit_news) to draw the boundary.

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?

There is no explicit when-to-use guidance and no exclusions. The closest thing is the implicit framing that this is for keyword lookup, which leaves the agent to infer how it differs from muhabbit_news or muhabbit_events.

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