remove_artist_tag

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

Annotations already convey destructive and idempotent nature, so the description's added value is the authentication requirement and the 'one of your tags' ownership qualifier. It does not detail error handling or behavior for non-existent tags, but given annotations cover the safety profile, this is acceptable though not rich.

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 clear sentences followed by a compact parameter list. Zero filler, purpose front-loaded. The structure is efficient and scannable.

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 simple two-parameter destructive operation with annotations covering destructive/idempotent and an output schema, the description covers the essential prerequisites and parameter meanings. Edge cases are not described, but they are not critical for correct invocation given the schema and annotations.

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 has zero descriptions (0% coverage), so the description must compensate. The Args section provides minimal but acceptable definitions ('Artist name' and 'The single tag to remove'). It could add format constraints or case-sensitivity, but the basics are present.

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 action ('Remove one of your tags from an artist') with a clear resource. Stands apart from siblings like add_artist_tags (opposite action) and get_artist_tags (retrieval).

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?

Mentions the authentication prerequisite, which is critical. Does not explicitly name alternatives or exclude scenarios (e.g., removing multiple tags), but the verb and the sibling set make the intended use clear without confusion.

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