marketplace_usage_history

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

No annotations are provided, so the description carries full responsibility for behavioral disclosure. It does not mention pagination, result format, ordering, time range, or any caveats beyond the basic action. This is a significant gap for a query tool that likely returns a list of records.

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 a single sentence with no wasted words. It is appropriately terse for a simple tool and front-loads the key action and resource.

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 no output schema and no annotations, the description is incomplete. It doesn't describe the return value structure, pagination behavior, or usage context among many similar marketplace analytics tools. The agent would be uncertain whether to use this vs marketplace_key_usage or marketplace_usage_heatmap.

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 documents all parameters. The description adds minimal semantic context by stating 'for a tool or user', which loosely maps to toolId and userAddress, but doesn't clarify whether either is required or how they interact. 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 clearly states the action ('Get') and the resource ('usage history'), specifying the scope 'for a tool or user'. This distinguishes it from many siblings, though it doesn't explicitly mention the marketplace context or differentiate from similar analytics tools like marketplace_key_usage.

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?

No guidance is provided on when to use this tool versus alternatives, nor any exclusions or prerequisites. The description implies you can filter by tool or user but doesn't explain how to choose between the available parameters or what to do when both are provided.

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