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

Annotations already declare that this is a non-read-only, non-idempotent, non-destructive mutation in a closed-world context. The description adds useful behavioral context by noting that MCP approval requirements are organization-configurable while business workflow approvals always apply, though it still does not explain the activation effect, prerequisites, or reversibility.

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 short and front-loads the action with the resource. The second sentence adds approval context, though its wording is somewhat abstract and could be more directly tied to invoking activation.

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 tool is simple and has an output schema plus annotations, so the description does not need to explain return values or safety hints. However, it omits usage guidance and does not clarify the id parameter or what activation changes, leaving meaningful gaps for an agent selecting and invoking the tool.

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?

There is one required id parameter, but schema description coverage is 0%, and the description does not explain that the id identifies the criteria profile to activate. The tool name provides only weak implicit meaning, so the description does not compensate for the schema's lack of parameter documentation.

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 states a specific verb and resource: activate an investment criteria profile. It is clear what the tool does, but it does not explicitly differentiate this action from sibling operations such as update_criteria_profile, archive_criteria_profile, or delete_criteria_profile.

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 provides no guidance on when to use activation versus updating, archiving, or deleting a criteria profile. The approval-related sentence gives context about approvals but does not tell the agent when this tool is the correct choice.

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