search_blog

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

Annotations declare readOnlyHint=true and idempotentHint=true. The description adds that the tool is 'Pure read-only, deterministic for a given KB snapshot' and explains the TF-IDF ranking, tokenization of multi-word queries, and the score threshold (0.001) for date sorting, providing behavioral context beyond 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?

The description is concise with two paragraphs and a structured behavior matrix. The first sentence front-loads the main purpose, and every sentence adds essential detail without redundancy.

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?

Given that an output schema exists, the description does not need to detail return values. It covers all key aspects: purpose, parameters, behavior, tag filtering, and read-only/deterministic nature, making it fully informative for an agent.

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?

Input schema has 100% description coverage, with each parameter already explained (e.g., query tokenization, tag filter, sort behavior, n bounds). The description adds value by tying parameter interactions in the behavior matrix, clarifying conditional behaviors that the schema cannot capture.

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 states 'Search the Sovereign AI Blog for articles matching a natural language query' with a specific verb ('Search') and resource ('blog articles'). It distinguishes from siblings like 'get_article' (single article) and 'list_tags' (tag discovery) by its focus on search and listing.

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 behavior matrix explicitly details when to use each sort option: for empty query, sort=date_desc; for non-empty query, sort=relevance gives TF-IDF ranking, sort=date_desc gives filtered results. It also mentions optional tag filtering, guiding the agent on parameter combinations.

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