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

Annotations already declare readOnlyHint and openWorldHint, so safety is covered. The description adds that results are brand-scoped and return identifying slugs, which is useful context beyond the annotations, though it doesn't discuss pagination or result volume.

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?

Front-loaded with the core resource and scope, then workflow context. Slight redundancy between 'usable as the model param on chrono24_search' and 'This is the discovery endpoint for that param', costing a bit of efficiency.

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 single-param discovery endpoint with an output schema present, the description supplies everything needed: scope, input source, and how the output is consumed downstream. Nothing an agent needs to call it correctly is missing.

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 the schema already says 'Brand slug from chrono24-brands'. The description reinforces the slug origin and tie-in to chrono24_brands, adding a small amount of cross-tool meaning but largely restating 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?

States a specific action (list every model/collection Chrono24 has for one brand) plus the resource and examples, and distinguishes itself from siblings by naming chrono24_search and chrono24_brands. An agent can immediately tell this enumerates models for a given brand.

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 positions the tool in the workflow: it is the discovery endpoint whose slug output feeds the 'model' param on chrono24_search, and its input comes from chrono24_brands. This is a complete when-to-use chain with prerequisites named.

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