segnals_get_listing

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

With no annotations provided, the description carries full transparency burden. It discloses the required authorization scope and outlines what the tool returns (details, strategy config preview, performance report). It does not mention rate limits or other behavioral traits, but for a simple read operation the disclosure is adequate.

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 extremely concise with three sentences, each serving a distinct purpose: stating functionality, usage guidance, and example with scope. No extraneous words.

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?

Given the tool's simplicity (single parameter, no output schema, no nested objects), the description covers purpose, usage, scope, and parameter example. It might optionally mention that the listing ID comes from browsing, but overall it is complete enough for an agent to invoke correctly.

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 input schema covers 100% of parameters with a description for listing_id. The description adds minimal extra value beyond the schema, showing an example call and mentioning it's from marketplace (already implied). Baseline 3 is appropriate as schema does the heavy lifting.

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 retrieves details for a specific marketplace listing, including strategy configuration preview and performance report. It uses specific verbs and resource, and the sibling tool 'segnals_browse_marketplace' is implicitly distinguished (browse lists multiple, get retrieves one).

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 advises using this tool to evaluate a strategy before copying it, providing a clear use case. It also states the required scope 'read:marketplace'. While it does not explicitly list when not to use or name alternatives, the context of sibling tools implies alternatives like browse or copy.

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