demand.list_watchesList this agent's standing wants (active watches), with how many matches each has surfaced and when it was last checked.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already indicate readOnlyHint=true. Description adds detail about output fields (matches count, last checked) beyond annotations, providing good behavioral context.
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?
Single sentence, front-loaded with purpose, no wasted words. Every part 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 parameterless read-only tool with no output schema, the description fully covers what the tool does and what it returns. No gaps.
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?
No parameters, so schema coverage is 100%. Description adds meaning by specifying what is listed (standing wants with matches and last checked), compensating for lack of parameter info.
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 it lists standing wants (active watches) with match counts and last checked time, using specific verb 'list' and resource. It distinguishes from siblings like create_watch or cancel_watch.
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?
Implies usage for viewing active watches, but no explicit when-to-use vs alternatives like browse_wants or get_want. Sibling tools exist but no guidance provided.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Several tools have overlapping purposes, e.g., create_want vs demand.create_want, get_want vs demand.get_want, and browse_wants vs search_listings vs search_products vs demand.search. Although descriptions attempt to differentiate, the presence of near-duplicates will likely confuse an agent.
Mix of naming conventions: some tools use 'demand.' prefix, others do not. Most follow verb_noun pattern (e.g., create_want, search_listings), but 'my_agent_profile' deviates. Inconsistent prefix usage reduces predictability.
18 tools is on the higher side but still within reasonable bounds for a commerce platform. However, several tools are redundant (e.g., create_want/demand.create_want), inflating the count unnecessarily.
Covers core demand-side workflows: creating/searching wants, listings, products, and outcome tracking. Missing update operations for wants and listings, but no critical dead ends for basic use cases.