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

Annotations already declare readOnly, idempotent, non-destructive and closed-world behavior, so the safety profile is covered. The description adds only the return summary ('best matches with their urls'); it does not disclose ranking behavior, whether results are capped or truncated, or what an empty result set looks like.

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 zero filler; the search scope is front-loaded and the return statement follows immediately. Nothing is redundant with the title or annotations.

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 simple three-parameter search tool with strong annotations and no output schema, most of what an agent needs is present. The gaps are the undocumented limit semantics and the mismatch between 'essays' in the description and 'posts' in the enum, which could cause a wrong kind value to be chosen.

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 33%, so the description must compensate. It partially does by enumerating the content kinds ('essays, publications, projects and measured results') that map to the kind enum, though the wording 'essays' does not match the enum value 'posts'. The limit parameter and its 1-25 cap are left entirely to the schema.

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 names a specific verb and resource ('Keyword search across essays, publications, projects and measured results') and adds the return shape ('best matches with their urls'). It implicitly separates itself from the list_* siblings by being keyword-driven rather than enumerating, though it never names an alternative.

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?

Usage is only implied: the word 'keyword' suggests this is the tool for free-text lookup, which contrasts with the sibling list_* tools. There is no explicit statement of when to prefer this over list_posts or get_post, and no guidance on query formulation beyond the schema example.

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