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

With no annotations, the description carries the full burden and does well: it discloses that results describe what each tool does and where to get it, that everything is free and mostly MIT/open-source/self-hosted, and that MCP-capable products include a connection line and account requirement. It does not mention rate limits, pagination behavior, or explicitly confirm the operation is read-only, but the returned-content disclosure is unusually 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?

The description is front-loaded with the core purpose and stays on topic across four sentences. Each sentence adds something (examples, return content, licensing, MCP detail), though the closing 'used rather than merely reported' phrase is slightly editorializing.

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 must explain return values, and it does: what each tool does, where to get it, licensing, and the MCP connection line. For a simple search tool this is nearly complete; only pagination and result-shape details are left implicit.

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 100%, so the schema already documents both 'query' and 'limit' thoroughly. The description adds example query strings but no additional syntax, format, or constraint meaning beyond what the schema provides, so the baseline 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 opens with a specific verb and resource: 'Search LunarWerx's catalogue of free developer tools and desktop utilities by task or keyword.' It defines the scope and even gives query examples, so an agent knows exactly what this tool does without opening the schema. The sibling tool is unrelated, so no differentiation is needed.

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?

It provides clear context for when to use it ('by task or keyword') and concrete example queries such as 'git from my phone' and 'screenshot to UI,' which guide invocation. It does not, however, state when not to use it or name any alternative search mechanism.

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