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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the read-only behavior is covered. The description adds useful contextual behavior: account-level state can span multiple artists, making this tool inappropriate for single-artist platform confirmation. It could go further by describing what the returned overview contains, but the output schema likely covers that.

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 description is front-loaded with the core use case, then provides precise exclusions and alternatives. Every sentence earns its place; there is no filler or vague boilerplate.

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?

Given the output schema exists, the description does not need to explain return values. It fully covers invocation conditions, required intent behavior, exclusions, and sibling routing, which is complete for a read-only account-overview 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?

Schema description coverage is 0%, so the description must compensate. It does so for the required intent parameter by explaining that it should match the explicit account question, and the prose lists the relevant concerns (organizations, artists, platform connections) that map to the intent enum. The optional format parameter is not discussed, but json/summary are self-explanatory.

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 names a specific verb and resource: it is for explicit questions about the signed-in Dynamoi account itself (who is logged in, organizations/artists accessible, account-level platform connections). It also explicitly distinguishes itself from sibling tools like dynamoi_list_artists and dynamoi_get_platform_status, so there is no ambiguity about what this tool is for.

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 description gives crystal-clear when-to-use guidance and equally clear when-not-to-use guidance. It names the exact alternatives (dynamoi_get_platform_status for artist-specific onboarding, dynamoi_list_artists for enumeration) and explicitly forbids using this tool as a generic context-check before answering unrelated questions.

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