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

Annotations already state readOnlyHint, openWorldHint and non-destructive, so safety is covered. Beyond that the description discloses nothing: not whether results are snippets or full pages, whether it covers only Stripe-hosted content, or how many results come back.

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?

A single front-loaded sentence with no filler. It is efficiently sized, though the brevity stems partly from under-specification rather than discipline.

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 annotations and a fully described schema, the core mechanics are documented, but for a tool whose main risk is being confused with stripe_api_search the missing sibling differentiation leaves a real invocation gap. An output schema is absent, so return-shape expectations remain unset.

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%, with all three parameters documented including the language enum and the search_only_api_ref flag, so baseline is 3. The description adds no parameter meaning beyond the schema.

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?

Names a specific verb and resource ('Search Stripe's official documentation and support articles'), so the agent knows it retrieves prose docs rather than account data. However, it never distinguishes itself from the closely named siblings stripe_api_search and stripe_api_details, both of which sound like documentation/API lookups.

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 on when to choose this over stripe_api_search, stripe_api_details, or stripe_api_read, and no mention of when to set search_only_api_ref. The agent must infer the routing decision entirely.

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