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

With no annotations, the description carries the full burden and delivers: it discloses the operation is queued for verification and "never applied automatically," plus authentication requirements (SSID_API_KEY or Bearer token, $15/mo Pro key). These are the exact non-obvious behaviors an agent needs before invoking a mutation-style tool.

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?

Purpose and constraints are front-loaded and every sentence is functional, but the trailing pricing/auth sentence is dense and packs plan cost, env-var name, Bearer option, and a free-tier note into one clause. Slightly crowded, though nothing is truly wasted.

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?

No output schema exists, and the description covers the important outcome (queued for verification, not applied). It does not describe what happens after submission (confirmation, review timeline, or error cases for invalid sources), which is a minor gap for a 4-parameter submission 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?

Schema coverage is 100%, so the baseline is 3, but the description adds real meaning beyond the schema: it constrains sourceUrl to official manufacturer sources (not aggregators/forums) and specifies the slug format via ssid.ai/routers/<slug>. Enum values for field are left to the schema, which already documents them.

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?

States a specific verb ("Propose a fix") and an enumerated resource (default gateway IP, username, password, credential type, reset steps) scoped to ssid.ai router models. An agent can immediately distinguish this submission tool from the read-oriented siblings (get_router_defaults, check_router_compliance, lookup_mac).

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?

Explicitly states the conditions and constraints: an official manufacturer source URL is required ("never an aggregator/forum"), the slug must come from ssid.ai/routers/<slug>, and a paid Pro key is needed while "the three read tools stay free." This routes the agent to the right tool and sets prerequisites without inference.

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