Search Decision State

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

With no annotations provided, the description bears full responsibility for behavioral disclosure. It only states the search action but omits details such as whether the search is across all sessions or limited to the current one, the order of results, or any side effects. This lack of transparency leaves the agent with significant unknowns.

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, front-loaded sentence with no redundant information. Every word serves a purpose, and it is appropriately sized for the tool's simplicity. This exceeds the requirements for conciseness.

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 the tool's simplicity, the description is too sparse. It lacks details about search scope, output format, and behavior with empty queries. For a search tool, more context (e.g., 'searches across all sessions' or 'returns matching decisions and reflections') would improve completeness.

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%, meaning the description does not elaborate on any parameters. It mentions 'query text' but does not explain that the 'query' parameter is the search string or that 'limit' controls result count. The description adds no value beyond the raw schema.

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 'Search prior decisions and reflections by query text' clearly states the action (search), the resource (prior decisions and reflections), and the method (by query text). It differentiates from sibling tools like get_state (which retrieves current state) and record_decision (which creates data). However, it could be more precise about what 'state' encompasses.

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 no guidance on when to use this tool versus alternatives such as get_session or get_state. It does not mention exclusions or contexts where search_state is not appropriate. A user must infer usage from the name and siblings.

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