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

The description discloses the scope and that each engagement includes its current state, and 'List' implies a read-only operation. However, with no annotations, it does not mention whether the result is paginated, ordered, limited, or if there are any side effects or error conditions beyond the generic 200 response.

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?

The description is concise and front-loaded, with the core purpose in a single sentence. The included 'Responses' section is generic boilerplate but does not significantly bloat the description.

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, parameterless list operation, the description is largely complete: it identifies what is listed, whose engagements, and that current state is included. It does not specify response fields or ordering, but given the absence of an output schema and the simple nature of the operation, the description is sufficient.

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?

The input schema has zero parameters, so there are no parameter descriptions needed. The description adds context by mentioning the signed-in consultant, which clarifies the implicit auth scope, but otherwise there is little parameter-specific meaning to add.

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 clearly states the action ('List'), the resource ('adoption engagements'), and the scope ('the signed in consultant'), plus that each item includes its current state. It is specific enough, though it does not explicitly differentiate from related sibling tools like adoption_get_adoption_summary or adoption_get_report.

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 guidance on when to use this tool versus the sibling tools, nor any explicit conditions, exclusions, or alternatives. The description implies usage when a list of engagements is needed, but it does not state when not to use it or what distinguishes it from similar list/get tools.

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