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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds the matching semantics (tool names and aliases), but says nothing about return shape, ordering, or the 25-item cap behavior beyond the schema. Adequate but not rich.

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 scoping definition front-loaded and the usage cue second; every clause earns its place and no filler is present.

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 two-parameter filtered list with no output schema, the description covers what is returned (use cases) and when to reach for it. It could note result ordering or whether multiple tools can be combined, but nothing critical 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 only 50% — the 'tool' param is documented but 'limit' has no description. The description compensates partially by clarifying that the tool param accepts ids, common names, and aliases (claude-code, n8n, Cursor, etc.), but it adds nothing about limit semantics or matching behavior (exact vs. fuzzy).

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 verb (List) and resource (use cases) with a precise scoping condition (those naming a consumer tool), which naturally distinguishes it from latest_use_cases and search_use_cases. It does not explicitly name a sibling or contrast with one, so it falls just short of the top score.

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?

"Useful when the user already picked a stack" gives a clear triggering condition for choosing this tool over the broader search/list siblings. There is no explicit when-not guidance or named alternative, but the context is unambiguous.

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