The $149 reviewed Evidence Pack: one narrow civic/infrastructure question, answered with a source trail. Includes today's real desk capacity.
This tool declares no required parameters. Add optional parameters from the input schema as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {},
"name": "evidence_pack_offer"
}
}| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Changes observed during successful MCP inspections.
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries the full burden of explaining side effects and call semantics. It states price and contents, but does not disclose whether the tool is read-only, whether calling it initiates a purchase, or what the caller actually receives as a result.
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 compact and front-loaded with the distinctive price and pack name. It has no filler, though the phrase 'today's real desk capacity' is unexplained and could have been clarified within the same concise format.
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 agent knows neither the return value nor the tool's place in the evidence-pack workflow. The description reads like a product blurb rather than an API contract, leaving the agent unsure of the outcome of invoking the tool.
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 tool has zero parameters and the schema has complete coverage, so there is no parameter ambiguity for the agent. The description adds useful context about what the pack contains, though the mention of a 'narrow civic/infrastructure question' could imply an input that is not actually captured by the schema.
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 identifies a specific resource, the $149 reviewed Evidence Pack, and summarizes its contents, but it never states the tool's action. There is no verb such as 'returns,' 'offers,' or 'creates,' so an agent must infer the purpose from the tool name rather than from the description.
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 given for when to call this tool versus alternatives such as evidence_pack_submit or document_text. The description distinguishes the product by price and contents, but it does not state a condition like 'use this to present the offer; use evidence_pack_submit to accept it.'
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.