list_system_routes_duplicate

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false. The description adds no behavioral context beyond 'Read System' and 'GET', which are already implied by the annotations. It does not disclose what happens or what special behavior the 'duplicate' endpoint has.

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 very short and front-loaded, but it is under-specified rather than efficiently informative. 'Read System.' adds little value on its own, and the HTTP path only identifies the endpoint without explaining its semantics.

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 there are no parameters and an output schema exists, the description fails to explain the endpoint's purpose, what 'duplicate' refers to, or how it relates to list_system_routes. The annotations cover safety but not the semantic context needed for correct 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?

The input schema has zero parameters, so there is no parameter semantics burden on the description. The baseline of 4 applies as no parameter documentation is needed.

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 states a verb ('Read') and the HTTP path '/api/v1/system/routes/duplicate', but it does not explain what the tool returns or what 'duplicate' means in this context. It is too vague to distinguish this from the sibling list_system_routes, so the agent cannot infer the tool's actual purpose.

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 usage guidance is provided. The description gives no indication of when to choose this tool over list_system_routes or other list_* siblings, nor any conditions or alternatives.

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