remnawave_subscription_page_configs_list

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

With no annotations, the description must fully disclose behavioral traits. Only '(read)' is stated, implying safety but offering no details about side effects, rate limits, permissions, or what the response contains. The 'read' label is insufficient for a complete behavioral profile.

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 extremely short (one sentence), which is concise but lacks important details. It earns a mid score because while it is not verbose, it fails to provide enough information to be useful.

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?

Given the tool has four parameters, no output schema, no annotations, and many sibling tools, the description is severely incomplete. It does not explain what subscription page configs are, what the list returns, how to use the parameters, or how this tool relates to other subscription_page_configs tools.

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 0% description coverage, and the description adds no meaning to the four parameters (payload, confirmToken, responseMode, mutationApproved). Without any explanation of their purpose or valid values (except responseMode's enum), the agent cannot infer proper usage.

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 'list (read)', clearly indicating it is a read operation to list subscription page configs. This distinguishes it from siblings like 'get' (single retrieval) and 'create'/'delete'/'update' (mutations). However, it does not specify the scope (e.g., all configs or filtered) or provide any additional context, so it is clear but minimal.

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 guidance is provided on when to use this tool versus alternatives. For example, there is no mention of when to list all configs versus getting a specific one, or any prerequisites or context. The description solely repeats the tool name and action.

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