Get Retrospective Process Group

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=true, so the safety profile is fully covered; the description contributes no additional behavioral context beyond 'by id', which is already implied by the required parameter. No mention of error behavior for missing ids or whether an `include` expansion changes payload size.

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 short sentence with zero filler and the key qualifier ('by id') front-loaded. It is efficient, though arguably under-specified rather than maximal conciseness.

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?

An output schema exists and the annotations cover the read-only safety profile, so the description need not explain return values. Still, for a getter surrounded by similarly named retrospective siblings, the absence of any routing or expansion guidance leaves the definition minimally viable.

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%, so both `id` and the `include` enum are documented in the schema, including the unusual note that this tool has no `retrospective_process_group_id` argument. The description adds nothing beyond 'by id', so the baseline 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?

Clear specific verb ('Retrieves') plus resource ('Retrospective Process Group') qualified by 'by id', so the agent knows exactly what the tool returns. However, it does nothing to distinguish it from the many sibling getters, notably get_retrospective_process and get_retrospective_step, which sit in the same domain.

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 alternatives (get_retrospective_process, list_retrospective_processes) and no prerequisites such as needing a valid id. The agent must infer usage entirely from the name.

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