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

Annotations already declare readOnlyHint=true and openWorldHint=false, and the description is consistent with that. It adds genuinely useful behavioral context about the fee model (founder rate applies only above founder_rate_minimum_cents, null when absent, otherwise the usual 10%, and whether Stripe's cut comes from the user's share), plus the important instruction that returned URLs are for the user to open rather than for the agent to fetch. It does not cover what happens when the user has no selling setup at all, which is a notable gap for a status tool.

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?

The content is front-loaded with the main purpose, but it arrives as one very long sentence packed with nested parentheticals about fee edge cases. The density makes it hard to scan, and the fee-model detail could be structured more cleanly or deferred, though most of it does carry real 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, the description must carry the burden of explaining return values, and it does so thoroughly, including the non-obvious fee and founder-rate semantics. Only the empty/non-seller state and error behavior are left unaddressed, which is a minor gap for a single-parameter read-only tool.

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?

There is a single parameter with 100% schema description coverage, and the schema fully explains the 'context' analytics string. The description adds nothing about it, which is acceptable given full coverage, so the baseline of 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?

The description clearly establishes this as a read of the signed-in user's selling setup, enumerating the specific facets returned (handle, connected repositories, payouts, listing count, platform fee, Stripe fee handling, founder rate minimum). It is a specific resource read rather than a tautology, though it never explicitly names how it differs from siblings like my_listings or my_earnings, which overlap in subject matter.

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?

The phrase 'and where to set up the rest' plus the closing note that 'The URLs are for the user to open in a browser' implies the intended use: diagnosing onboarding gaps and directing the user to complete setup. However, there is no explicit when-to-use or when-not-to-use guidance, and no statement of how this differs from checking listings or earnings directly, so the agent must infer the routing.

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