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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description adds only the 'public details' scope, which is mild added context; it says nothing about not-found behavior, rate limits, or size of payload. Appropriate for the lower bar set by annotations, but 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?

One short sentence with the verb, scope, and identifier requirement front-loaded. No filler or redundancy.

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 single-parameter read tool with an output schema (return shape need not be described) and annotations covering safety, the description covers what an agent needs to invoke it. Only edge-case behavior such as missing/invalid ids is left unstated.

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 100% and the single parameter is documented as 'Numeric artist id.' The description repeats 'numeric id' without adding format constraints, ranges, or examples. Baseline 3 when the schema does the work.

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 verb ('Fetch') and resource ('full public details for a single artist'), scoped to one record by id. The 'public' qualifier usefully narrows what data is returned. It does not explicitly differentiate from siblings, but the resource nouns (artist vs. editor/product/event) already make the distinction unambiguous.

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 phrase 'by their numeric id' implies you must already have an id, which hints at when to use it, but there is no explicit when-to-use, prerequisite, or fallback guidance (e.g., what to do if only a name is known, or which sibling handles listing/searching artists). Usage is inferable rather than stated.

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