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

Since no annotations are provided, the description carries the full burden. 'Browse' implies a read-only operation, and 'Supports filtering and sorting' gives some capability context. However, it does not disclose pagination details, default behavior, or return format. It is adequate but not rich, so a score of 3 is appropriate.

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 two sentences long, front-loaded with the core purpose and immediately followed by an alternative direction. Every sentence adds value with zero waste.

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 description clearly explains the tool's role and distinguishes it from a key sibling. For a 7-parameter listing tool with no output schema, it covers the essential selection criteria. It could mention pagination or return format, but the parameter schema handles pagination, and the listing behavior is simple enough that a 4 is warranted.

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?

The schema description coverage is 100%, so the baseline is 3. The description's mention of 'filtering and sorting' is generic and does not add specific parameter semantics beyond what the schema already provides. Thus, no uplift beyond baseline.

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 clearly states the tool's purpose: 'Browse services in the Remno marketplace.' This includes a specific verb ('Browse') and resource ('services in the Remno marketplace'). It also distinguishes itself from the sibling tool ae_discover_services by noting it is for filtering and sorting rather than semantic search.

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 explicitly provides usage guidance: 'For semantic search, use ae_discover_services instead.' This tells the agent when not to use this tool and names the alternative, which is exactly what the dimension requires.

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