search_recent_entries

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

With no annotations, the description carries full burden. It states entries are 'fetched from the API' but doesn't disclose whether this searches a local cache, how recent is 'recent', how pagination works (beforedate parameter unexplained), or any rate limits. The behavioral model is barely hinted.

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 a single sentence, which is concise but lacks structure. It does not front-load key information (e.g., what search is performed, constraints). It is under-specified, making it ineffective.

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 4 parameters (1 required), no annotations, and many sibling tools, the description is grossly incomplete. It fails to explain the search mechanism, result format, pagination, or relationship to other similar tools. The output schema exists but is not referenced.

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 0%. The description adds no meaning to any of the 4 parameters: query, limit, journal, beforedate. Required field 'query' is not explained (what kind of query string?). The default values are not contextualized.

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 the vague verb 'search' without specifying what fields are searched (subject, body, tags?). It mentions 'most recent' but doesn't clarify the scope compared to siblings like 'search_cached_entries' or 'list_entries'. The tool name and description are nearly tautological, offering little differentiation.

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?

No guidance is provided on when to use this tool versus the many sibling tools (e.g., search_cached_entries, list_entries). There is no indication of preconditions, alternatives, or exclusions.

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