create_artist

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

With no annotations provided, the description bears full responsibility for behavioral disclosure. It adds that the artist will be flagged for AI review, which is key behavioral context. However, it does not mention any specific permissions needed, rate limits, or the exact creation process, though the core behavior is adequately described.

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 three short sentences, front-loaded with the primary purpose and critical usage condition. No extraneous information is included; every sentence adds value.

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 complexity (11 parameters, no output schema), the description covers the key caveat (manual review) and usage prerequisite. It does not explain return values or error handling, but for a creation tool with such detailed schema, the description is sufficiently complete for an agent to use 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 coverage is 100%, so the baseline is 3. The description does not add additional parameter-level information beyond what is already in the schema. The schema itself provides detailed descriptions for all parameters, so the tool description does not need to repeat them.

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 clearly states the action ('Create a new artist') and the resource ('in BNDY'). It distinguishes from siblings like 'search_artist' by specifying that this tool should only be used if no matches are found, which also differentiates from 'edit_artist'.

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 explicitly provides a usage condition: 'Only use if search_artist found no matches.' This gives clear guidance on when to use this tool versus alternatives, and also mentions the consequence ('Artist will be flagged for manual review').

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