operator_lost_brands

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

Annotations already provide readOnlyHint=true. Description adds 'churn signal' context implying comparison over time. No contradictions; additional behavioral context is minimal but sufficient given annotations.

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, front-loaded with purpose and usage hints. No wasteful text; every 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?

Covers purpose and usage but omits output format, pagination, and filter behavior. With 10 parameters and no output schema, more detail on limit and filtering semantics would improve completeness.

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 description coverage is 50%, but tool description does not add any parameter-level details. Undocumented params like limit, brand_contains, last_seen_week_to, first_seen_from/to are left unexplained, forcing reliance on schema which is incomplete.

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 'Show brands an operator recently stopped selling' with specific verb and resource. Distinguishes from sibling tools like operator_new_brands by focusing on lost brands. Includes example queries.

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?

Explicitly tells when to use with example queries ('what brands did this seller drop', 'operator churn'). Lacks guidance on when not to use or alternatives, but positive guidance is strong.

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