get_plugin_embed_code

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

No annotations are provided, so the description carries the full burden. It states that the tool 'Genera el codigo de instalacion' (generates installation code), implying a read/generation operation. However, it does not disclose any additional behaviors such as authentication requirements, side effects, or rate limits. The description is adequate but minimal.

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 two short sentences with the key information front-loaded. Every sentence serves a clear purpose: stating what the tool does and when to use it. No unnecessary 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 (one parameter, no output schema, no nested objects), the description covers the essential information. It could be improved by hinting at the output format (e.g., 'returns the embed code as a string'), but this is not critical for a straightforward retrieval tool.

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% with enum descriptions. The description adds value by mapping the enum values to full names ('chat' -> 'Chat Web', etc.) and clarifies that the code is for installation. However, this is largely a restatement of the schema's enum descriptions, so the added value is modest.

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 the action ('Obtener codigo embed') and resource ('plugin'), and specifies three specific plugin types (Chat Web, Product Q&A, Doc Q&A). It distinguishes from sibling configuration tools by focusing on retrieval of the embed code for installation.

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 states when to use: 'cuando el usuario necesite el codigo para instalar...' (when the user needs the code to install). It does not provide negative guidance or alternatives, but the context is clear enough for an agent to decide.

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