global_search

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

With no annotations, the description must convey behavioral traits, but it only states the basic purpose. It omits details such as result format, pagination, performance implications, or whether it searches text only or all fields. The existence of an output schema does not fully compensate for missing behavioral context.

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 concise sentence that efficiently conveys the core purpose. It is appropriately front-loaded and contains no superfluous information. A slightly more structured format could improve readability but current is acceptable.

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?

Though the tool performs a broad search across all projects and nodes, the description lacks completeness. It does not mention the scope's impact on performance, result limits, or how to narrow results. For a high-impact search tool, this is insufficient guidance.

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%, so the parameter is already documented. The description adds little value beyond paraphrasing the schema, stating 'using a global keyword' which aligns with the 'query' parameter. No additional constraints or format details are provided.

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's function: search across all nodes in all projects using a global keyword. It uses a specific verb 'search' and a resource 'all nodes in all projects', distinguishing it from siblings that search specific domains like API or database.

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 implicitly suggests usage for global keyword searches but provides no explicit guidance on when to use this tool versus alternatives like search_api or search_db_usage. No when-not-to-use or prerequisites mentioned.

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