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

Annotations already declare readOnly/openWorld=false/destructive=false, so safety is covered. The description adds real value by explaining the demand metric and the crucial caveat that listing is not a build promise. It doesn't mention ordering, pagination, or return shape, so it earns a solid but not exceptional 3 against the lower annotation bar.

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 tight sentences with the resource and its semantics front-loaded and zero filler. Could be marginally sharper but is efficiently sized.

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?

With no output schema, the description does the job of conveying what a call returns – items plus distinct-owner demand/vote counts. Combined with full schema coverage this is nearly complete, missing only ordering/pagination 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 coverage is 100%, so both parameters (status enum, passport_token) are fully documented in the schema. The description adds no syntax or filtering detail beyond what the schema already provides, so baseline 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 resource (the roadmap of agent-requested items) and what data is included: demand counts from distinct paying owners. It is clearly a read/list operation, distinguishable from vote_roadmap and make_wish by implication, though it never names those 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?

Usage is only implied – an agent infers this is for browsing the roadmap. There is no explicit when-to-use vs. vote_roadmap/make_wish guidance, and the status-filter parameter's purpose isn't tied to a scenario. The 'not a promise to build' caveat is helpful but is interpretive, not routing guidance.

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