search_posts

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

No annotations provided, but description itself states 'Read-only' and describes return format (titles+ids). Could mention pagination or rate limits, but overall good for a search tool.

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 concise sentences, front-loaded with 'Read-only' and purpose. No wasted words.

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?

Covers purpose, usage, and return format. Lacks parameter details for 3-param tool with no output schema. Adequate but has clear 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 0% (no descriptions in schema), yet description does not explain individual parameters like query format, limit usage, or pub meaning. Only implicit mention of query via full-text search. Does not compensate for low 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 clearly states tool is for full-text search of posts ('search_posts'), specifies it is read-only, and distinguishes from sibling 'list_posts' for chronological browsing.

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?

Explicitly says use for keyword discovery, not for chronological browsing (use list_posts). Also notes that results are only titles+ids and suggests calling get_post/get_post_content for details.

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