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

Annotations already declare readOnlyHint and openWorldHint, but the description adds real context the annotations cannot: subscriber-only values are omitted (a data completeness caveat), the cost is $0.002 USDC per successful call, failed calls are not charged, and payment goes through x402 on Base/Solana/Arc. It does not detail rate limits or what an x402 payment flow requires operationally.

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?

Purpose and scope are front-loaded in the first clause, and the long parenthetical field list is dense but each item earns its place by telling the agent exactly what data is available. The pricing sentence is compact. Slightly list-heavy but not padded.

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 readOnly/openWorld annotations and an output schema present, the description need not explain return shape, yet it still enumerates payload contents and flags the subscriber-data truncation. Combined with the pricing/billing terms, an agent has nearly everything needed; only explicit sibling routing is missing.

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%, so all three parameters (type, ticker, exchange) are already documented with examples and defaults. The description's mention of 'US stock, ETF or mutual fund' loosely maps to the type values but adds no syntax or default information beyond the schema. Baseline 3 applies.

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: Morningstar quote page data for a US stock, ETF or mutual fund, and enumerates the exact fields returned (star rating, key stats, top-10 holdings, analyst headline). This makes it clearly distinguishable from generic quote siblings like finance_finviz or finance_yahoo_finance, though it never names a sibling explicitly.

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 only implied by the field list – an agent can infer this is for equity/fund fundamentals from a Morningstar source. There is no explicit when-to-use, when-not, or pointer to an alternative tool among the many finance_* quote siblings. The 'subscriber-only values are omitted' note is a useful boundary but not usage routing.

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