browse_radar_projects

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint=false, so the safety profile is covered. The description adds the set of browseable facets but does not disclose pagination behavior, default limit, or how filters combine; given the strong annotation coverage, this is adequate but not exceptional.

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 concise and free of fluff, but it is under-specified for the complexity of the tool. A single short phrase cannot meaningfully describe an 18-parameter browsing interface, so the brevity comes at the cost of usefulness.

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?

The presence of an output schema reduces the need to describe return values, but the description still omits critical context: how filters relate, which fields are mutually exclusive, what the default behavior is, and what 'filtered projects' means. For a read-only exploratory tool with this many parameters, the definition is incomplete.

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 0%, so the description must compensate for 18 undocumented parameters. It only maps loosely to a few of them (ranking, collection, category, scenario, topic) and offers nothing about value formats, defaults, combinations, or locale/limit behavior. This is far below what is needed for an 18-parameter tool.

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 uses a specific verb ('Browse') and identifies the resource ('radar projects'), while enumerating the main browse dimensions: rankings, collections, categories, scenarios, topics, and filtered projects. It does not explicitly contrast itself with sibling tools like browse_radar_skills, but the word 'projects' makes the primary resource 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 gives no guidance on when to use this tool versus alternatives such as search_ai_projects, get_radar_overview, or browse_radar_skills. The word 'Browse' weakly implies exploratory use, but there are no explicit conditions, exclusions, or comparisons to help an agent select among siblings.

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