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

Annotations declare readOnlyHint=true and openWorldHint=false, so the safety profile is already covered. The description adds genuinely useful context by enumerating the returned profile sections, which matters because there is no output schema to describe the payload. It omits failure behavior (e.g. unknown composer) but is otherwise strong.

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 front-loaded sentence that opens with the core purpose and then lists the payload contents without filler. The enumeration is dense but every item conveys what the caller will receive.

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 one-parameter, read-only lookup with a fully documented schema and no output schema, the description's enumeration of return contents largely covers what an agent needs. Only the relationship to the search sibling and error/not-found behavior are left implicit.

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 already documents that it accepts a name or a Pauline identifier, with examples. The description adds no syntax, matching, or disambiguation detail beyond the schema, 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 names a precise resource — a complete profile of a Pauline composer — and enumerates exactly what the profile contains (biography, key works, accessibility rating, links), which is far more specific than the title alone. It does not, however, explicitly contrast itself with the sibling chercher_compositeurs, so an agent must infer that this is the detail-fetch counterpart to the search tool.

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?

There is no statement of when to use this tool versus the siblings. It never tells the agent to resolve a name via chercher_compositeurs first, nor when a profile lookup is appropriate rather than a concert or record query. Usage must be inferred entirely from the name and the listed contents.

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