genius_get_artist

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

Since annotations are absent, the description must cover behavior. It only implies a read operation ('Get') and fails to disclose authentication requirements, rate limits, or any other behavioral traits.

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 a single sentence with no unnecessary words. It is concise, though it could benefit from additional detail without sacrificing brevity.

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?

Without an output schema, annotations, or detailed parameter info, the description is incomplete. It leaves the agent without knowledge of return format, error handling, or usage context for a relatively simple 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?

With 0% schema description coverage and no parameter explanations in the description, the agent must rely solely on the schema. The phrase 'by ID' weakly maps to the 'id' parameter but does not clarify its type or the optional 'api_key'.

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 'Get a Genius artist by ID' clearly states the verb, resource, and method. It is specific but does not differentiate from sibling tools like genius_artist_songs or genius_search.

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?

No guidance is provided on when to use this tool versus alternatives. There is no mention of prerequisites or context for usage.

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