add_station

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

With no annotations, the description carries the full burden of behavioral disclosure. It reveals that this is a POST-based submission and that only name and url are required, but it does not disclose authentication requirements, validation rules, duplicate handling, idempotency, or what response the agent should expect after submission.

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 efficient sentence with no filler. It front-loads the core action, then gives the endpoint and the only truly necessary requirement. 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?

This is a mutating tool with no annotations, no output schema, and nine parameters, yet the description covers only the action and the two required fields. It omits important operational context such as response format, error behavior, authentication, and optional parameter semantics, so the definition is not complete enough for reliable invocation.

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 0%, so the description must compensate. It adds that only name and url are required, which is marginally useful, but it provides no meaning for the remaining seven optional parameters (tags, state, country, favicon, timeout, homepage, language), leaving their semantics almost entirely undocumented.

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 operation ('Submit a new station to the directory') with a specific verb and resource, and even includes the endpoint (POST /json/add). This strongly distinguishes it from the sibling search/list/vote tools, so an agent can easily identify what this tool does.

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?

The description gives clear context: use this tool when submitting a new station. While it does not explicitly name alternatives or state when not to use it, the purpose itself is distinct enough from the read-oriented sibling tools that the usage context is reasonably clear.

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