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

No annotations are provided, so the description must carry the behavioral disclosure. It transparently lists what the response contains (portfolio, pricing tiers, specialties, ratings, reviews), which indirectly implies a read-only fetch. It does not mention error handling or auth requirements, but for a simple 'get by ID' operation, the main behavior is unambiguous.

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?

A single sentence with the critical scope (single artist by ID) front-loaded, followed by the specific data fields. No filler or repetition. Every clause earns its place.

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-resource getter with one parameter and no output schema, the description adequately outlines the expected return content. It does not detail the exact response structure, but given the low complexity and no output schema, the high-level field list is sufficient for an agent to know what to expect.

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% — the schema already documents artistId as 'The ID of the artist'. The description adds that it returns a profile for a single artist, but that is essentially redundant with the tool name and schema. No new parameter-level meaning is added, so the baseline of 3 applies.

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 ('Get'), a precise resource ('full profile of a single Sharaloge artist by ID'), and enumerates the key content (portfolio, pricing tiers, specialties, ratings, reviews). This clearly distinguishes it from siblings like search_artists (which would return a list) and reserve_booking (which is about bookings).

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 gives clear context: it is for fetching a single artist's profile when an ID is known. It does not explicitly mention alternatives or exclusions, but the 'by ID' qualifier implicitly separates it from search_artists. No explicit when-not-to-use guidance exists, so it lacks the full directness of a 5.

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