query_resume_history

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

With no annotations, the description discloses key behavioral traits: 'Fast, deterministic substring matching' and 'exact keyword or phrase.' This goes beyond the minimal purpose statement but doesn't detail return format or edge cases like case sensitivity.

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 the purpose front-loaded and the alternative mentioned succinctly. Every sentence earns its place with no redundant 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?

The simple tool has no output schema, and the description covers purpose, behavior, and alternative usage. It does not describe the return format or pagination, but these are less critical for a straightforward search tool.

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 already fully describes the query parameter with 100% coverage, so the baseline is 3. The description adds meaning by emphasizing 'exact keyword or phrase' and 'substring matching,' which clarifies how the parameter should be used.

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 the tool searches Matt's work history, role bullet points, and experience highlights for an exact keyword or phrase. It also distinguishes itself from semantic_search_history, making the purpose 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?

Explicitly instructs to use this tool for exact keyword or phrase matching and recommends semantic_search_history for conceptual or paraphrased queries. This provides clear when-to-use and when-not-to-use guidance.

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