segnals_browse_marketplace

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

Discloses that results are neutrally sorted and performance data is labeled as live or backtest. Since no annotations are provided, the description carries the burden; it implies a read-only operation but does not explicitly state no side effects. Overall, adequate transparency for a browse tool.

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?

Four sentences, each adding value: purpose, return details, use case, and example with scope. No wasted words, front-loaded with the main action.

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?

Covers purpose, return value type, sorting, use case, scope, and example. Lacks detail on the structure of each listing beyond performance data, but given the simplicity and no output schema, it is reasonably complete.

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 100% and parameters are well-described in the schema. The description adds only an example usage with 'page', which is helpful but not necessary. Per rubric, baseline 3 is appropriate.

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' targeting the 'strategy marketplace', clearly distinguishing it from siblings like 'segnals_get_listing' (specific listing) and 'segnals_my_listings' (own listings). It also states the action: 'Returns available strategy listings' and the use case: 'discover strategies the user can copy'.

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?

States when to use ('discover strategies the user can copy') and requires a scope ('read:marketplace'). Does not explicitly mention when not to use or alternatives, but the context of siblings makes it clear this is for browsing the whole marketplace.

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