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

No annotations are provided, so the description carries the burden. It usefully discloses the directory size (800+) and that results come back with full structured metadata, but says nothing about read-only nature, result ordering, or behavior when filters are combined, and pagination is only implied by the limit param.

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 core purpose front-loaded and the return behavior second. Every clause earns its place with no redundancy.

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 parameter-rich search tool with no output schema, the description is nearly sufficient: it names the corpus, the filter surface, and the return shape. What it lacks is usage routing against its four siblings, which an agent would still need to infer.

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 every parameter is already fully documented in the schema, including the enum values and the unknown-value exclusion rules. The description's enumeration of filter dimensions adds no syntax or semantics beyond what the schema provides, so the 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?

States a specific verb (Search) and resource (the BroFindAI directory of 800+ AI tools), and enumerates the filterable dimensions so the agent knows exactly what it searches over. It implies a boundary with get_tool_details by noting it returns 'full structured metadata,' but never names a sibling tool, so it falls short of explicit differentiation.

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 gives no when-to-use or when-not-to-use guidance and does not point to any alternative. It never mentions list_categories or list_tags as vocabulary helpers (that hint lives only in the tags schema field), so an agent gets no routing help from the description itself.

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