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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered externally. The description adds nothing beyond that — no auth/scope requirements, no note on whether the status is tenant-level or user-level, and no indication of caching or freshness of subscription state.

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?

It is short, but the opening sentence is duplicated verbatim, which is pure waste, and the only substantive information (the operation ID and the describe_operation pointer) is buried after the repetition rather than front-loaded.

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 two-parameter nested-object tool with zero schema documentation and no output schema, the description is far too thin — the agent learns nothing about the request shape or the returned fields. The pointer to describe_operation and execute_read is the sole mitigating element, so it is not entirely inadequate.

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% and both parameters (`query` as an open additionalProperties bag and empty `params`) are undocumented. The description does not compensate at all, only deferring to describe_operation for 'native request schemas', leaving the agent guessing what query keys are accepted and whether any are required.

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 only restates the HTTP path and repeats it verbatim ('GET /api/subscription/status. GET /api/subscription/status.'), which is the title with slashes added. It gives no indication of what data is returned (plan, seats, renewal date, payment state) and does not distinguish it from siblings such as get_subscription_trial_status, get_subscription_billing_check, or get_subscription_usage_summary.

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 when-to-use guidance and no stated alternative — with eight sibling subscription endpoints, the agent has no basis for choosing this one over them. The only actionable pointer is 'describe_operation provides native request schemas', which explains how to discover the request shape rather than when to call this tool.

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