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 only restates the search scope and does not clarify whether this searches a local corpus, returns snippets or full pages, or has any limitations. While 'search' implies a non-destructive action, the agent is left without meaningful behavioral detail beyond the purpose itself.

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 filler. Its list of content types is slightly redundant ('documentation' plus many subcategories), but it remains compact and easy to scan.

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?

For a simple two-parameter search tool, the description is mostly sufficient for selection and invocation. However, with no output schema, it does not state what the agent should expect as a result, and it lacks explicit usage routing. These are gaps but not crippling ones given the tool's simplicity.

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 100%, so the schema already documents both parameters adequately. The description adds some context by listing what kind of queries are supported, but it does not materially enrich the parameter semantics beyond the schema's own examples and the topic enum.

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 uses a specific verb and resource: 'Search official RubiConnect documentation.' It also enumerates concrete content types (API references, character limits, console navigation, how-to guides), which makes the tool's scope immediately clear and distinguishes it from siblings like search_images and send_message.

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 implies when to use the tool: whenever an agent needs official RubiConnect documentation or feature guidance. However, it does not explicitly state when not to use it or name an alternative, so an agent must infer this from the resource scope rather than receive direct routing guidance.

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