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

Goes well beyond the annotations by disclosing cost (free), link lifetime (does not expire), the sign-in-to-Geocode-AI handoff before the portal opens, the no_subscription failure mode, and the auth requirement (API key or connected account). It leaves one gap: it never clarifies that generating the link itself does not mutate billing state, which is the natural question raised by readOnlyHint=false.

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?

Front-loaded with the core deliverable and packed with high-value facts in a compact space. The middle sentences become somewhat run-on, stacking link lifetime, sign-in flow, and failure mode without separation, but almost no wording is wasted.

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 parameters and no output schema, the description must carry the entire burden, and it does: it covers what is returned (a URL), its lifetime, the sign-in step, the cost, the auth prerequisites, and the specific error case. An agent has everything needed to call this and set expectations for the user.

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?

The tool takes zero parameters, so there is no parameter semantics to explain and the baseline of 4 applies. Nothing in the description is needed to disambiguate inputs, and nothing misleading is present.

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?

States a specific verb+resource (produce a Stripe Customer Portal link for the account owner) and enumerates exactly what the recipient can do with it: download invoices, change card/billing details, switch plans, cancel. This clearly separates it from siblings like create_checkout_link, get_subscription, and get_pricing.

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?

Usage is implied by 'for the account's owner' plus the no_subscription failure case, which tells the agent this only applies to accounts with a past paid plan. However, it never explicitly says when to prefer this over create_checkout_link or get_subscription, so the alternative selection is left to inference.

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