capabilities.search

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

No annotations provided, so the description bears full responsibility. It mentions 'ranked' (implying sorted results) but does not disclose safety, authentication needs, or what happens on failure. For a search tool, it lacks behavioral clarity.

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?

Extremely concise—one sentence with a front-loaded directive ('start here'). However, conciseness here sacrifices essential information, making it barely adequate.

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 4 parameters and no output schema, the description fails to explain parameter usage, return format, or edge cases. It is incomplete for effective agent decision-making.

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 must add meaning. It only says 'by keyword', ignoring the 4 parameters (query, kind, limit, domain). The description provides no parameter details beyond the schema titles, which are already visible.

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?

Clearly states the action (search), resource (capabilities), and scope (ALL of Blender). The phrase 'start here' suggests it's the entry point. However, it does not differentiate from sibling tools like 'api.search' or 'rna.search', which might have overlapping purposes.

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 says 'start here' implying primary use, but no explicit when-to-use or when-not-to-use. With siblings like 'api.search' and 'rna.search', the lack of guidance on alternatives is a significant gap.

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