Get Tool Help

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

No annotations exist, so the description must fully disclose behavioral traits. It only states the basic function, without indicating whether it is read-only, what the output format is, or any side effects. This is inadequate for a tool that presumably returns help content.

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 concise sentence with no wasted words. It directly states the tool's purpose and is front-loaded.

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?

The description is minimal. For a help tool, it should explain the nature of the help (e.g., format, content) and any constraints. No output schema is provided, and the text fails to compensate. The Spanish language adds a potential barrier for English agents.

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 coverage is 100% and the description of parameter 'toolName' in Spanish matches the parameter description. The description adds no extra semantic value beyond the schema, but the baseline for high coverage is 3.

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 'Obtiene información detallada sobre una herramienta específica' clearly states the verb (gets) and resource (detailed information about a specific tool). It distinguishes from sibling tool 'list-available-tools' by focusing on a single tool, but does not explicitly contrast. The language is Spanish, which may hinder an English-speaking AI, but the purpose is still clear.

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?

No usage guidelines provided. The description does not mention when to use this tool versus alternatives like 'list-available-tools', nor any prerequisites or context. The agent receives no guidance on selection.

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