attacher_fonction_bouton_embed

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

With no annotations provided, the description carries full burden for behavioral disclosure. It states the tool attaches custom JavaScript code to a button, implying a mutation operation, but doesn't mention permissions required, side effects, error conditions, or what happens if the function fails. This leaves significant gaps for a tool that executes user-provided code.

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, efficient sentence that directly states the tool's purpose without unnecessary words. It's appropriately sized for a tool with clear parameters documented elsewhere.

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 tool that attaches executable JavaScript code to UI elements (a potentially complex and sensitive operation), the description is insufficient. With no annotations, no output schema, and minimal behavioral context, it doesn't provide enough information about security implications, error handling, or expected outcomes to guide safe and effective use.

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 description coverage is 100%, so the schema already documents all four parameters thoroughly. The description adds no additional semantic context about parameters beyond what's in the schema, such as format examples or constraints. The baseline score of 3 reflects adequate but minimal value addition.

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 ('attache une fonction personnalisée') and target resource ('à un bouton d'embed existant'), making the purpose understandable. However, it doesn't differentiate from the sibling 'enregistrer_fonction_bouton' or 'supprimer_fonction_bouton', which appear related to button functions.

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 provides no guidance on when to use this tool versus alternatives like 'enregistrer_fonction_bouton' or 'creer_embed'. It mentions the target is an existing embed button but doesn't specify prerequisites, constraints, or appropriate contexts for invocation.

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