station_infoStation metadata.
| Name | Required | Description | Default |
|---|---|---|---|
| station_id | Yes |
| Name | Required | Description | Default |
|---|---|---|---|
| body | No | Raw text response from API | |
| format | No | Indicates response is plain text (non-JSON) |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The description adds no behavioral context beyond what the annotations already declare (readOnlyHint, idempotentHint, etc.). It does not mention return format, pagination, or any special behavior. The annotations cover safety, but the description contributes nothing.
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 only two words, but this is under-specification rather than effective conciseness. It lacks a full sentence and any useful structure, providing no meaningful information to the agent.
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?
Although the output schema exists and the tool is simple, the description is too minimal to be complete. It does not explain the tool's role, what 'station' refers to, or how the returned metadata could be used. The description fails to provide sufficient context for reliable tool selection.
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?
With 0% schema description coverage, the description carries the full burden for parameter semantics, yet it says nothing about the 'station_id' parameter. There is no explanation of what IDs are valid, how to obtain them, or what the parameter represents.
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 'Station metadata' is essentially a restatement of the tool name/title 'Station Info' with no action verb. It does not specify what operation is performed (e.g., retrieve, list, get) and does not distinguish this tool from any siblings.
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 on when to use this tool or when to consider alternatives. The description provides no context, prerequisites, or exclusions, leaving the agent to guess the intended use case.
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 are near-duplicates or have fuzzy boundaries: ask_pipeworx_beta explicitly matches ask_pipeworx exactly, the raw data tools (daily_data, hourly_data, event_data, latest, reservoirs) all read as generic 'get data' operations, and the five polymarket_* scanners overlap in opportunity-finding. The verbose descriptions help for many composite tools, but an agent can still easily select the wrong variant.
The naming is predominantly consistent lowercase snake_case with strong prefixed families (ask_pipeworx*, polymarket_*, pipeworx_*, scan_*) and clear verb_noun actions. Minor deviations like noun-only latest/reservoirs, ask_pipeworx lacking a separator, and generate_llms_txt keep it from a 5.
37 tools is well above the heavy threshold, and the count is inflated by redundant meta-tools, three router variants, six overlapping generic data fetchers, and six prediction-market tools. Many tools are purposeful, so it is not an extreme mismatch, but the surface would be much cleaner at roughly 20-25 tools.
The set covers the core data lifecycle well: discovery (discover_tools, suggest_questions), lookup (ask_pipeworx), grounding/validation (ask_pipeworx_grounded, validate_claim, search_within), entity workflows (resolve_entity, entity_profile, recent_changes, compare_entities), plus memory and subscription CRUD. Minor gaps like no explicit fetch-by-citation tool and a limited subscription type set prevent a 5.