Activates a profile for a number

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

Annotations already disclose that this is a non-read-only, idempotent, non-destructive operation with open-world effects. The description adds only the HTTP verb and path, not what activation changes, whether it switches out another active profile, permission requirements, or the response shape.

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 two short sentences with the purpose front-loaded and no wasted prose. It is appropriately sized for a simple endpoint, though the endpoint parenthetical is the only extra detail.

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 mutation with annotations and complete schema coverage, the description covers the basic purpose. However, it leaves key semantic gaps: what activation does and what the required body `id` refers to, which matters for correct invocation.

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 the baseline is 3. The description adds the endpoint path showing number_id as a path parameter, but does not clarify that the required body field `id` is the profile identifier or explain its role.

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: activating a number profile, with the endpoint path. It is clear enough to understand the operation, but it does not explicitly differentiate this tool from nearby siblings such as placetel_activate_number, placetel_deactivate_number, or placetel_create_number_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 only restates the tool's purpose and gives no guidance on when to use it versus alternatives or prerequisites. There is no mention of when not to use it, whether a profile must already exist, or how it relates to activate_number/deactivate_number.

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