Buscar operaciones en la API

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

Annotations declare readOnlyHint and openWorldHint, and the description confirms a read-only search behavior. No contradictions or surprises. It adds context about the breadth of searchable operations beyond what annotations provide.

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 concise, consisting of two front-loaded sentences. Each sentence provides essential information: what the tool does and when to use it. No wasted words.

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 simplicity (read-only search, two parameters, no output schema) and the annotations (readOnlyHint, openWorldHint), the description is complete. It covers the purpose, usage, and next steps, leaving no gaps.

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 describes the keyword parameter (required) and limit (optional integer 1-100). The description provides an example for keyword but adds no additional meaning for limit. Schema description coverage is 50%, which is not low (<50%), so baseline 3 applies. The example is helpful but not transformative.

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 that the tool discovers Beebole operations (queries and mutations) by keyword. It specifies the resource (87 queries + 745 mutations) and the action (search by name or description), distinguishing it from sibling tools that perform specific operations.

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 explicitly instructs to use this tool when no curated tool exists for a needed operation, and then follow up with beebole_describe_operation and beebole_graphql. This provides clear guidance on when and how to use it.

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