search_by_date_range

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

The description complements annotations by specifying 'semantic search', which is not conveyed by readOnlyHint or openWorldHint. It accurately portrays a read-only, date-constrained operation without contradicting 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 two sentences, front-loaded with the core purpose, and every word contributes. No extraneous information.

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 and annotations are present, the description covers the tool's purpose, parameters, and usage context adequately. No missing critical details.

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?

With 100% schema coverage, the description adds minimal value beyond the schema, only reinforcing 'ISO 8601 dates' which is already in examples. It does not deeply explain any parameter's semantics or edge cases.

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 is a 'semantic search scoped to items saved between two dates', specifying verb, resource, and scope. It distinguishes from sibling search tools by explicitly limiting to a date range.

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 description provides usage context with 'Useful for reviewing what you captured during a specific period or project', indicating when to use it. However, it does not explicitly mention when not to use or contrast with alternatives.

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