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

Annotations already establish read-only, idempotent, non-destructive behavior, so the description's job is to add context. It does this by specifying the search scope and stating that results are ranked cards containing title, URL, tags, date, reading time, and summary—important because no output schema is provided. This discloses the result contract without repeating annotation data.

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 short sentences with the purpose front-loaded and the result shape in the second sentence. No filler or redundant restatement of the tool title.

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 read-only search tool with a full schema and annotations, the description covers the main missing piece—output format—since there is no output schema. It doesn't address when to prefer a sibling tool, which is a minor completeness gap for an ecosystem with ten similarly scoped 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 the schema already explains query, limit, and section, including defaults, cap, and enum values. The description adds no additional parameter-level meaning beyond the schema, so it meets the baseline for high 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?

The description uses a clear verb-resource pair ('Search Karandeep Singh's blog') and specifies the content scope (DevOps/AWS articles and cheatsheets) plus the returned card fields. It doesn't explicitly distinguish search_posts from sibling tools like browse_by_tag or related_posts, though the name and search semantics make the distinction inferable.

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 gives no guidance on when to use search_posts versus alternatives such as browse_by_tag, list_recent, or list_topics. It only implies search usage through the verb and the required query parameter; there are no exclusions or condition-based routing.

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