find_decisions_by_context

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

No annotations exist, so the description carries the burden. It indicates substring matching behavior and the fields searched, but does not mention case sensitivity, result format, performance implications, or whether it is read-only. It conveys basic behavior adequately but lacks depth.

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?

Single sentence, no filler. The version number is minor but not detrimental. Every word contributes meaning, with no redundancy.

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 simplicity (one param, no output schema, no annotations), the description covers essential purpose and scope. However, the lack of output description (what does the tool return? list of decisions?) leaves a gap for agents needing to know how to use the result.

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 coverage is 100% for one parameter. The description adds context by naming the three fields searched, which supplements the generic 'Substring to search for' in the schema. However, it does not provide format or syntax details beyond that.

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 performs a substring search across three specific fields (context, decision, consequences), giving a precise verb and resource. It distinguishes from generic search tools like search_nodes by targeting decisions, but does not explicitly set it apart from other decision-related tools like get_decision or list_decisions.

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 on when to use this tool versus the many sibling search tools (e.g., fuzzy_search, semantic_search, boolean_search). No exclusions, prerequisites, or context provided. The description merely states what it does, not when it is appropriate.

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