artist_reissue_detector

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

With no annotations, the description carries the burden of behavioral disclosure. It adds a useful quota/cost signal: one paginated /artists/{id}/albums walk, which helps the agent anticipate expense. It also explains grouping behavior, though it does not disclose exact return shape or edge cases.

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?

Two sentences, front-loaded with the main action and expected output, followed by a concise quota note. No filler or repetition of schema details.

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 read-style detection tool, the description covers purpose, expected output concept, and quota behavior. There is no output schema, so a bit more detail on the returned grouping structure would be ideal, but the response_format parameter and the grouping statement provide enough for an agent to invoke it correctly.

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 75%, so most parameters are already documented. The description does not add much param-level detail, but it does imply that artist_id maps to the /artists/{id}/albums walk. The undocumented max_results is not compensated for, but overall the schema carries the parameter burden.

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 ('Detect') and resource (alternate versions in an artist's release titles), and defines the key outcome: group by base title and identify canonical releases vs variants. This distinguishes it from sibling tools like duplicate_saved_versions or album_edition_lint without needing extra context.

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 implied clearly: use when you need to find reissues, deluxe, remaster, or lived editions within an artist's discography. However, it does not explicitly state when to prefer this over similar sibling tools or mention exclusions, so the agent must infer the decision from the purpose.

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