Leer una página de la documentación de CyberArk/Idira

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

With no annotations, the description discloses the domain restriction ('solo ese dominio') and behavioral actions (fetching, cleaning, converting to Markdown). It does not discuss error handling or edge cases, but for a simple read-only fetch tool, this is adequate transparency.

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 sentence, front-loaded with the action, resource, and output. Every phrase serves a purpose, and there is no redundant padding.

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 one-parameter tool with no output schema, the description adequately covers what the tool does, the domain constraint, the return format (Markdown), and the intended use. No significant missing information is apparent.

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 schema already fully describes the URL parameter with 100% coverage, including the domain. The description adds context about output format and purpose, but the domain restriction is already present in the schema, so the added semantic value is limited.

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 ('Trae y limpia') and identifies the resource (docs.cyberark.com pages) and output (Markdown). It clearly distinguishes from the sibling tool by targeting a specific page rather than searching.

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?

It provides a clear use case: to answer questions by citing official documentation instead of inventing answers. However, it does not explicitly mention the sibling search tool or state when not to use this tool, so it lacks explicit alternatives.

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