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

No annotations exist, so the description carries the full burden: it discloses that some fields are conditionally present and that 'full' changes the payload shape, which is genuine behavioral context. It never states that this is a side-effect-free read, nor what happens for an unknown or still-generating role_id.

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?

Two sentences with no filler, and the returned payload is front-loaded ahead of the detail-mode qualifier. The first sentence is long but each enumerated field 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?

With no output schema, the description must carry return-value disclosure, and it does enumerate the fields plus the conditional courses and the extra full-mode fields. Remaining gaps are error behavior and how role_id is obtained, which are secondary for a simple read.

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 50%: role_id is documented nowhere, and the description only implies it selects 'one generated role profile' without stating its origin or format. The detail explanation largely restates the enum description already in the schema, adding conditionality but no new meaning.

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 a specific resource (one generated role profile), and enumerates the payload fields, so the agent knows exactly what comes back. The qualifier 'generated' separates it from the public/job-description siblings, but no sibling is named and it never says how it differs from list_my_roles or get_public_role.

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 when-to-use statement, no prerequisites, and no mention of alternatives, despite siblings like list_my_roles, check_role_status and get_public_role that could plausibly be confused with it. The only conditional given ('when the generation asked for them') describes payload variance, not tool selection.

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