update_activity_selector

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

No annotations provided, so description carries full burden. It discloses one error case (returns available names if location not found), supports both AB and XT, and mentions env vars. Missing details on success response, permissions, destructive nature, or idempotency.

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?

Four sentences covering purpose, usage, edge case, environment, and type support. Concise without being terse; each sentence adds value.

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 with 3 parameters, nested objects, and no output schema, the description covers purpose, when to use, an error behavior, and environment setup. Missing success response details but otherwise complete enough 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 coverage is 100% and parameter descriptions are thorough. The description adds context about when to use the tool but doesn't enrich individual parameter meanings beyond what's in the schema. Baseline 3 is appropriate.

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 tool updates location selectors in an Adobe Target activity, with an example use case (when primary selector doesn't match intended target). It differentiates from siblings like update_activity_name but doesn't explicitly contrast with update_activity, so not a 5.

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?

Provides explicit guidance on when to use ('Use this when the activity's primary location selector does not match...'). Does not give when-not-to-use or alternatives, but the context is sufficient. The mention of automatic environment loading is helpful setup info.

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