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 safety is covered. The description adds nothing beyond that: no note on what configuration fields are exposed, whether secrets are redacted, or whether it requires specific portal/Stripe setup, and it contains no contradictions.

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 redundancy, and the remaining content (operation ID, schema pointer) is boilerplate rather than front-loaded useful information.

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?

With no output schema, no parameter documentation, and no annotation gaps to fill, the description still leaves the agent without a plain-language account of what is returned or how to form the query. The deferral to describe_operation partially mitigates but does not make the definition self-sufficient.

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 the two parameters (a freeform 'query' object and an empty 'params' object) are undocumented. The description does not explain what query keys are accepted or that params must be empty, only deferring generically to describe_operation.

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 endpoint path 'GET /api/payment-portal/stripe-config' twice, which is essentially a tautology of the tool name and title. It never states in plain language that it retrieves the Stripe payment-portal configuration (keys, mode, capabilities, etc.), so an agent must infer purpose from the URL slug alone.

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 use this versus siblings such as describe_operation, execute_read, or the other payment-portal getters (bank_accounts, payout_configs, dashboard). The only hint is the pointer that describe_operation provides request schemas, which is not a when-to-use rule.

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