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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint, and the description adds useful behavioral context beyond those: it targets the currently displayed 'settled' Spotlight, includes labeled house advertisements, and explicitly states it does not bid or pay. No contradiction with the annotations exists.

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 short sentences with no filler. The core action and resource are front-loaded, and the clarifying note about not bidding or paying is concise and valuable.

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 read-only tool with one optional parameter, rich annotations, and an output schema, the description covers the essential invocation context. The only notable gap is the absence of explicit sibling differentiation, but the tool is otherwise adequately described.

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?

There is only one optional parameter, includeHouseAds, and its schema description fully covers its behavior (100% schema description coverage). The prose adds no parameter-specific detail, but the schema already provides enough meaning, so the baseline score of 3 applies.

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 states a specific verb and resource: it 'Read[s] the currently displayed settled public Spotlight' and further clarifies it includes labeled house advertisements. The phrase 'currently displayed' differentiates this from the sibling tools get_spotlight and list_spotlights, making the tool's scope clear.

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 the tool is for reading the current Spotlight and explicitly notes it does not bid or pay, which helps set expectations. However, it never names the sibling tools or states when to choose this over get_spotlight or list_spotlights, leaving some routing to inference.

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