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

Annotations already declare read-only, idempotent, non-destructive behavior. The description adds genuinely useful context beyond them: the data is privacy-thresholded and there is no payment, credit, or AI-call cost. It does not cover pagination or rate limits, but the output schema exists to handle return structure.

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 short sentences, front-loaded with the action and resource, followed by a clarifying cost statement. No filler; every clause earns its place.

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 low-complexity read-only tool with a fully described schema, rich annotations, and an output schema, the description covers purpose and a key behavioral fact (no cost/AI call). It is complete enough for correct invocation, though it could mention filtering intent for the optional parameters.

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 the schema fully documents limit, market, and capability. The description adds no additional meaning about these parameters, which is acceptable when the schema does the heavy lifting, but it leaves no extra value on this dimension.

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 ('Read') and resource ('privacy-thresholded 30-day demand/supply and observed outcome signals'), making the tool's function clear. It does not explicitly contrast itself with any sibling in the large nexus_trade_* family, so an agent must infer that this is the read-only signals endpoint rather than a transactional 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?

There is no indication of when to call this tool versus alternatives such as nexus_trade_list_offers or nexus_find_tasks, nor any prerequisites or exclusion conditions. Usage is only implied by the verb 'Read' and the data being retrieved.

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