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

Annotations provide minimal behavioral info (no readOnlyHint, destructiveHint false), but the description adds context: it's a write operation restricted to non-FREE businesses, requires permission checks, and involves showing warnings. However, it doesn't detail what happens to existing pixels (e.g., overwrite or append) or side effects.

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 concise (two main sentences plus actionable instructions), but the instructions are somewhat detailed. The structure is logical, front-loading the purpose then prerequisites.

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 tool has a complex nested parameter (trackingPixels object with no schema description) and no output schema. The description covers access control well but omits details about parameter format, return value, and default behavior, making it incomplete for an agent.

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 has zero description coverage for its two parameters (communityId and trackingPixels object). The description does not explain the structure or expected keys/values of trackingPixels, leaving the agent uncertain about input format.

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 'Update advertisement tracking pixels for a managed community', specifying the verb (update) and resource (advertisement pixels), distinguishing it from general community update tools like update_community.

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 explicit step-by-step instructions: check business permissions via check_business_tool_access, note that FREE businesses cannot use it, show grace-period warnings and verified resubscribe links, and never proceed when access is blocked. This clearly guides the agent on when and how to use the tool.

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