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 safety profile is established. The description adds value beyond that by explaining the roster-vs-profile behavioral split and, notably, the semantic meaning of an empty response (brand-new user, route to recommendedNextActions rather than reporting 'no records found'). No contradiction with annotations.

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?

Four sentences, all earning their place: primary use case, artistId variant, exclusion routing, and empty-result behavior. Information is front-loaded with the main purpose first. Slightly dense as one paragraph, but there is no filler.

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?

For a tool with 4 optional params, an output schema, and 15 siblings, the description covers when to use it, what it returns, what it excludes, the artistId variant, and the empty-result edge case. Remaining gaps are minor: no mention of pagination behavior (limit/cursor) or the format enum, though those are optional and conventional.

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 carries the full burden for parameter meaning, but it only addresses artistId ('pass artistId when you need the full profile/readiness details for one artist'). It adds nothing for limit, cursor, or format — pagination semantics and the json/summary distinction are left completely unexplained.

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 states a specific verb+resource: listing artists/YouTube channels the user manages, and names the exact fields returned (billing status, active campaign count, role). It distinguishes itself from siblings by naming dynamoi_list_campaigns and dynamoi_get_campaign as the campaign-detail tools, and by contrasting roster-page output with full-profile output.

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?

Explicit when-to-use ('when the user wants to see which artists or YouTube channels they manage'), when-to-pass-artistId, and clear exclusions with named alternatives ('Do not use this for campaign details; use dynamoi_list_campaigns or dynamoi_get_campaign'). It even handles the edge case of an empty result with routing instructions to dynamoi_get_account_overview.recommendedNextActions.

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