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

Goes well beyond the annotations: it discloses that delete/archive paths fail, that is_archived writes are silently dropped, that renaming with a 'DELETE ME' prefix is the intended workaround, and that confirm=false is a preview. Annotations only say destructiveHint=true/idempotentHint=false. The one gap is that it does not say what the tool returns or whether the name is overwritten vs. appended.

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?

Front-loaded with the core action, then the when-to-use block, then per-parameter notes. Every sentence carries information, though the all-caps emphasis and the two-clicks detail in Events Manager are slightly more color than an agent strictly needs.

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 5-param mutation tool with an output schema already present, the description covers purpose, gating scenario, key parameter defaults, and the preview flag. Nothing required to call it correctly is missing, and return values are correctly left to the output schema.

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 0%, so the description must compensate, and it largely does: conversion_id's source is named, default_conversion_value=-1 is explained as 'keep current', and confirm=false is explained as preview. name and description are only implied by the opening sentence, so it stops short of full coverage.

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?

States the specific verb (renames) and resource (custom conversion) plus the secondary operations it supports (setting description and default conversion value). It also names the sibling that supplies the id (list_meta_custom_conversions), so an agent can distinguish it from create_meta_custom_conversion without opening either schema.

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?

Explicit 'USE THIS WHEN...' clause tied to a concrete scenario (a conversion set up wrong), plus a statement of what alternatives do not work (delete returns a permissions error, is_archived is silently ignored) and where the real removal happens (Meta Events Manager). No inference required.

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