remnawave_subscriptions_get_by_username

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

With no annotations, the description must fully disclose behavior. '(sensitive-read)' hints at read-only sensitivity but provides no details on error behavior, data scope, or side effects. Bare minimum.

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?

Extremely brief but at the cost of useful information. Every word should add value; here, the description is a mere restatement of the name with a one-word qualifier.

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 no output schema, no annotations, and a 0% schema description coverage, the description is critically incomplete. It fails to clarify what the tool returns, how to use the payload, or the role of confirmToken and responseMode.

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%, yet the description does not explain any of the 4 parameters (payload, confirmToken, responseMode, mutationApproved). Agents receive zero guidance on how to populate these fields.

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 almost tautologically restates the tool name with '(sensitive-read)' added. It does not explicitly state that it retrieves subscription info by username, nor what specific data is returned. Sibling tools like get_by_uuid and get_by_short_uuid are not distinguished.

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 alternative subscription retrieval tools (e.g., by UUID). No prerequisites or context for invoking are given.

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