subscriptions_get_connection_keys_by_user_id

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

No annotations are provided, so the description carries full behavioral burden. It discloses the return format (base64) and hints at auth via the '[Protected]' tag, but says nothing about permissions, whether keys are sensitive/rotatable, error behavior for unknown userId, or rate limits.

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 core sentence is short and front-loaded, but the raw 'GET /api/subscriptions/connection-keys/{userId}' route and the 'Tags: [Protected] Subscriptions Controller' boilerplate are noise that does not help an agent decide or invoke.

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?

For a single-parameter read tool with no output schema, the description covers purpose and output format adequately. It stops short on the behavioral/auth context an agent would want before calling a protected endpoint that returns credential-like keys.

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 100% and the single required userId is fully documented in the schema, so baseline 3 applies. The description's 'by user id' merely restates the schema and adds no format or constraint detail beyond what is already given.

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 specific verb and resource — 'Get connection keys (base64 format) by user id' — which is unambiguous about what is returned and how it is keyed. It does not, however, differentiate this tool from the many other subscriptions_* siblings that also retrieve subscription data by user/short uuid.

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?

There is no guidance on when to call this versus alternatives such as subscriptions_get_subscription_by_uuid or subscriptions_get_all_subscriptions. The only context offered is a raw HTTP route and a '[Protected]' tag, which implies authentication but not usage conditions.

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