search_profile

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

No annotations are provided, so the description carries the full burden. It does add useful behavioral context by mentioning that results are excerpts and that the tool is cheaper than get_profile. However, it does not disclose potential pagination, match semantics, or any constraints or side effects beyond the search being a read operation.

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 compact and front-loaded: the core action is in the first sentence, and the second sentence adds valuable usage guidance without excess. Every sentence earns its place.

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?

This is a simple one-parameter search tool and the output schema exists, so the description does not need to explain return values in depth. It covers purpose, usage context, and query semantics sufficiently, though fuller behavioral constraints such as result limits or exact/fuzzy matching would make it complete.

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 provides no description for the single 'query' parameter, but the description compensates by explaining that the term is searched for as a fact-check across profile documents. This gives the agent a clear mental model of what to pass, though exact matching behavior is not specified.

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 a specific verb ('Search'), a specific resource ('profile documents'), and the expected output ('matching excerpts'). It also distinguishes itself from the sibling get_profile by noting this is cheaper for checking a single fact.

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?

It explicitly says when to use this tool: 'when you only need to check one fact' and names the alternative (get_profile) that is better for fuller retrieval. The concrete example ('whether a specific tool, employer or metric appears anywhere') gives an agent clear decision criteria.

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