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

With no annotations, the description carries full behavioral burden (hence the higher baseline credit). It usefully discloses which fields are searched and that results include a snippet, but says nothing about result limits, ranking, pagination, or empty-result behavior.

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 with no filler; the action and match scope are front-loaded and the return shape follows immediately. Every clause earns its place.

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?

No output schema exists, so the description must cover return behavior and does so minimally ('matching posts with a snippet'). For a search tool with an unannotated read profile, missing result limits, ordering, and pagination leave gaps.

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 coverage is 100% and the single parameter is documented ('Keyword or phrase to search for'), so the baseline is 3. The description adds the meaningful detail that the keyword is matched across titles, descriptions, and full text, but no syntax or partial-match semantics.

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 gives a specific verb and resource ('Search blog posts') plus the match scope (titles, descriptions, full text). It implicitly distinguishes itself from list_posts and read_post by being keyword-driven, though it never names or contrasts those siblings.

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 routing to alternatives, despite list_posts and read_post being obvious candidates for browsing versus reading. The agent must infer that keyword matching is the selecting condition.

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