Ejecutar GraphQL crudo

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

Annotations already provide readOnlyHint=false, destructiveHint=true, openWorldHint=true. Description reinforces that it can modify data and adds context about full API coverage. It does not contradict annotations and adds useful behavioral context, though no further details on rate limits or auth.

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?

Description is extremely concise: two sentences covering purpose, usage pattern, and caution. No unnecessary words, information is front-loaded and relevant.

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 raw GraphQL tool with no output schema, the description does not mention the response format or potential errors. While the usage guidance is good, the lack of output information and variable details leaves gaps. The tool's complexity warrants a bit more description for completeness.

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?

Input schema describes 'query' well but lacks description for 'variables'. The tool description mentions 'variables' as optional but does not elaborate on format or constraints. With 50% schema coverage, the description partially compensates but could provide more detail, especially for variables.

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?

Description explicitly states when to use this tool ('Para operaciones sin tool curada') and suggests alternative discovery tools (beebole_search_schema, beebole_describe_operation). It also includes a caution about data modification, guiding appropriate usage.

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?

Description explicitly states when to use this tool ('Para operaciones sin tool curada') and suggests alternative discovery tools (beebole_search_schema, beebole_describe_operation). It also includes a caution about data modification, guiding appropriate usage.

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