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

The description explains important output behavior, including how baseline measurement versus reconstruction is reported and how non-comparable waves are handled. However, with no annotations, it does not explicitly disclose side effects or confirm that the tool is read-only, leaving some behavioral transparency burden unmet.

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, well-structured, and front-loaded with the core purpose. It avoids unnecessary detail while still covering important output semantics and an edge case, making it easy to parse and understand.

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?

The description gives a solid overview of the returned summary content, including overall, process area, movement, baseline provenance, and comparability. It lacks explicit response format details and parameter guidance, but remains sufficiently complete for an agent to understand what the tool provides.

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 description mentions 'one engagement' but does not explicitly explain the engagement_id parameter, its source, or how to obtain valid values. Schema coverage is 0%, so the description adds little beyond the parameter name and type.

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 that the tool provides an adoption summary against baseline for one engagement, including overall, process area, and movement. It also explains key output distinctions such as baseline provenance and comparability, making the tool's purpose unmistakable.

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 does not provide any guidance on when to use this tool instead of sibling tools such as adoption_get_report or adoption_list_engagements. There is no mention of use cases, prerequisites, or alternative selection criteria.

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