territory_set_seller_context

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

No annotations are provided, so the description carries the burden. It mentions that it automatically calls the 'Territory News AI enrichment engine', which is a behavioral trait, but does not disclose side effects (e.g., persistent mutation), permissions required, or error conditions. This is partial transparency.

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 two sentences, concise and well-structured. The primary action is stated upfront, and the additional detail about the enrichment engine is relevant. No unnecessary verbosity.

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?

Given no output schema and no annotations, the description should clarify return values and prerequisites, but it does not. It explains what the tool does and its effect, but omits details about what the caller receives (e.g., success confirmation, errors) or any input requirements beyond the parameters.

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?

The schema has 100% description coverage, so the baseline is 3. The description summarizes the parameters (Role, Target Segment, etc.) but adds no new semantic information beyond what the parameter descriptions already provide.

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's function: configuring or updating sales context. It also mentions the specific elements (role, target segment, etc.) and the effect (tailoring deal signals). This is specific and unambiguous.

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 implies usage for setting or updating context, but does not explicitly contrast with the sibling tool 'territory_get_seller_context'. It does not state when to use this over alternatives, leaving some ambiguity for an agent.

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