Call a reviewed read tool with its exact schema. Public cache: 300 s, selected stable reference tools 24 h; stale results are marked. Check original sources. Never forwards Ask974.re credentials or publishes.
| Name | Required | Description | Default |
|---|---|---|---|
| api_key | No | ||
| arguments | No | ||
| freshness | No | fresh accepts unexpired cache or waits for a new collection; it never returns stale data. | allow_stale |
| tool_name | Yes | ||
| provider_id | Yes |
Changes observed during successful MCP inspections.
Input schema / $schemaPrevious value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"Input schema / properties / freshnessAdded value: +{
+ "default": "allow_stale",
+ "description": "fresh accepts unexpired cache or waits for a new collection; it never returns stale data.",
+ "enum": [
+ "allow_stale",
+ "fresh"
+ ],
+ "type": "string"
+}Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already establish read-only, idempotent, non-destructive behavior, and the description adds meaningful context: public cache 300s, 24h for selected stable reference tools, stale results being marked, and a credentials policy. This goes beyond the structured hints without contradicting them.
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 short and front-loaded with the core action, followed by cache policy, verification advice, and credential policy. It is compact, though the last sentence is somewhat cryptic with the proper noun 'Ask974.re'.
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 dynamic dispatcher with five parameters, nested arguments, and no output schema, the description is incomplete: it does not explain how to discover valid provider_id/tool_name values, how arguments should be shaped, how api_key is used, or what the response contains. The cache and security notes are useful but not sufficient.
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 only 20%, so the description carries a heavy burden for explaining api_key, provider_id, tool_name, and arguments. It only hints that the call must use the selected tool's exact schema, leaving the meaning and relationship of the parameters largely implied.
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 opens with a specific action, 'Call a reviewed read tool', identifying the resource and dynamic dispatch nature. It is clear that this is a dispatcher for research-style read tools, but it does not explicitly distinguish itself from sibling tools such as read_research_source or list_provider_tools.
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 guidance about when to use this tool versus the many sibling research/read tools. The security line 'Never forwards... or publishes' is a constraint, and 'Check original sources' is post-hoc advice, but neither explains selection criteria or alternatives.
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.