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

Annotations already establish read-only, idempotent, non-destructive behavior; the description adds useful behavior beyond that: newest-first ordering and explicit inclusion/exclusion rules for house and removed ads. No statement contradicts the 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?

One compact sentence front-loads the core behavior and immediately adds the key scoping details (ordering, inclusion, exclusion) without extraneous text. Every clause adds information.

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 simple paginated list tool with an output schema, the description covers the essential operation, ordering, and content filtering. It does not explicitly clarify pagination semantics or define 'settled,' but the schema and sibling names cover most of the remaining context.

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 0%, and the description does not explain limit or offset. The names and constraints make the parameters reasonably guessable, but the description itself adds no meaning, and there is no compensation for the low schema coverage.

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 uses a specific verb ('Browse') with a clear resource ('settled public Spotlights') and gives distinguishing scope: newest first, including labeled house advertisements and excluding removed ads. This makes it clearly distinct from the get_spotlight/get_current_spotlight siblings.

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 wording implies this is the list/browse tool for settled public Spotlights, which differentiates it from the get tools, but it never explicitly says when to choose this over a sibling or when not to use it. Usage context is implied by 'Browse' and 'settled public' rather than stated.

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