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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description adds a useful behavioral note that existing commercial currency stays fixed, i.e. reading this does not mutate billing state, but says nothing about what happens when no country is set or what permissions are required.

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?

Three short sentences, front-loaded with the purpose, with zero filler. The 'currency stays fixed' line is slightly cryptic in a read-only context but still earns its place as a scoping clarification.

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?

An output schema exists, so return values needn't be explained, and the read-only nature is covered by annotations. However, for a lookup whose whole value is the semantic distinction of 'billing country,' the description leaves open what the value means for payouts and how to obtain a valid artistId.

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%, so the description must carry the burden and it does not — artistId is never mentioned, and there is no note on whether it comes from dynamoi_list_artists or dynamoi_get_account_overview. The UUID format and pattern in the schema are the only guidance available.

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 and resource ('Read the artist billing country') that is immediately distinguishable from a generic billing read. The clarifying line 'This is not tax residency' further narrows the concept, though it does not name a sibling tool the agent should use instead.

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 negative scope ('not tax residency') implies when the tool is and isn't appropriate, but no positive trigger is given for when an agent should call this vs. dynamoi_get_billing, dynamoi_get_account_overview, or dynamoi_list_available_countries. Usage is inferable but not stated.

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