search_kibana_api_paths

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It states the tool searches endpoints by keyword, but doesn't describe behavioral traits such as whether it's read-only, safe to use, what the output format looks like (e.g., list of paths, details), or any limitations (e.g., search scope, rate limits). For a tool with zero annotation coverage, this is a significant gap in transparency.

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, efficient sentence: 'Search Kibana API endpoints by keyword'. It's front-loaded with the core action and resource, with zero wasted words. Every part of the sentence earns its place by conveying essential purpose, making it highly concise and well-structured.

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 complexity (a search function with one parameter) and the lack of annotations and output schema, the description is incomplete. It doesn't explain what the tool returns (e.g., a list of endpoint paths, details, or matches), how results are formatted, or any behavioral context needed for effective use. This leaves significant gaps for the agent to understand the tool's full context.

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 input schema has 100% description coverage, with the single parameter 'search' documented as 'Search keyword for filtering API endpoints'. The description adds no additional meaning beyond this, as it only repeats the keyword concept without elaborating on syntax, format, or examples. Given the high schema coverage, the baseline score of 3 is appropriate, as the schema does the heavy lifting.

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 purpose: 'Search Kibana API endpoints by keyword'. It specifies the verb ('search'), resource ('Kibana API endpoints'), and mechanism ('by keyword'), which is specific and actionable. However, it doesn't explicitly differentiate from sibling tools like 'list_all_kibana_api_paths' or 'get_kibana_api_detail', which prevents a perfect score.

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. It doesn't mention sibling tools like 'list_all_kibana_api_paths' (which might list all endpoints without filtering) or 'get_kibana_api_detail' (which might retrieve details for a specific endpoint), leaving the agent to infer usage context. This lack of explicit when-to-use or alternative references results in minimal guidance.

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