set_location_filter

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

No annotations are provided, so the description carries the full burden. It discloses that the tool restricts alerts to a radius and applies to both individual and watch-all scans, but does not mention whether the filter is persistent, whether it overrides previous filters, or if any side effects exist. This is minimal transparency for a mutation tool.

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, each adding distinct value: the first states the primary action and the scope, the second clarifies applicability. No redundant or unnecessary words.

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 the tool's simplicity (4 params, no output schema, no annotations), the description is complete enough. It explains what the tool does and its scope. It could optionally mention that it returns a confirmation or affects subsequent alerts, but this is not critical.

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?

Parameter schema coverage is 100% with clear descriptions for each param (lat, lng, city, radius_km). The description adds a general statement about using city or coordinates but does not provide additional semantic detail beyond 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's purpose: to restrict restock alerts to SAQ stores within a radius. It specifies the verb 'restrict' and the resource 'restock alerts', and distinguishes itself by explicitly mentioning it applies to both individual SKU watching and watch-all catalog scans, differentiating from siblings like 'clear_location_filter'.

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 a geographic filter but provides no explicit guidance on when to use this tool versus alternatives (e.g., clear_location_filter) or when not to use it. No context about prerequisites or conditions is given.

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