search_entries

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

No annotations exist, so the description carries the full burden. It states the tool returns up to 3 entries per request and supports pagination, but does not explicitly disclose that it is a read-only operation with no side effects. This partial disclosure is adequate but not comprehensive.

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 extraneous information. The first sentence clearly states the purpose, and the second provides the key behavioral constraint (max 3 items) and pagination mechanism. Efficient and front-loaded.

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 search tool with a complex nested input schema and no output schema, the description is somewhat minimal. It covers pagination but does not explain the structure of the 'query' parameter (though schema covers it), nor does it describe the return value format or content type filtering. Adequate but not fully comprehensive.

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?

The schema covers all parameters with descriptions (100% coverage), so the description adds limited new value. It reiterates the limit and skip behavior, which the schema already defines. The nested query object is well-documented in the schema, leaving little need for additional explanation.

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 clearly states it searches for entries using query parameters, which distinguishes it from sibling tools like get_entry that retrieve a single entry by ID. The verb 'Search' and resource 'entries' are specific and unambiguous.

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?

Provides explicit guidance on pagination: maximum 3 items per request and use of skip parameter. However, it does not compare with alternatives like get_entry for when to use search versus direct retrieval, though the name implies query-based filtering.

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