yd_excluded_sites_update

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

Discloses that the operation replaces the entire list (not additive), which is a key behavioral trait. However, with no annotations, it lacks details on permissions, idempotency, or rate limits. The description is minimal but not misleading.

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?

Two sentences with zero waste. Front-loaded with the primary action and key behavior. Every word is necessary.

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?

Adequately covers the tool's purpose and key behavior for a simple update operation with no output schema. Lacks mentions of prerequisites (e.g., campaign existence, permissions) but remains sufficient for an agent to understand the operation.

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?

Input schema covers all parameters with descriptions (100% coverage). The description adds value by explaining 'Replaces entire list' for the 'sites' parameter, but no additional meaning for 'campaign_id' or 'client_login' beyond the schema.

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?

Clearly states the verb 'Set' and resource 'excluded sites (blocked placements)' for a campaign, and distinguishes from sibling tools like yd_excluded_sites_get (retrieval) and yd_blocked_ips_update (IP blocking). The phrase 'Replaces entire list' adds specific scope.

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?

No guidance on when to use this tool versus alternatives such as yd_excluded_sites_get or yd_blocked_ips_update. Does not provide when-not or alternative tools.

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