Creates a new profile for a number

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

Annotations already declare readOnlyHint=false, destructiveHint=false, idempotentHint=false and openWorldHint=true, so the mutating/non-destructive profile is covered. The description adds only the endpoint path; it says nothing about duplicate-name behavior, permission requirements, or what happens to an existing profile on the same number — meaningful gaps for a create operation flagged as non-idempotent.

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?

It is a single short sentence plus an endpoint parenthetical, so nothing is buried or bloated. The parenthetical API path is of marginal value to an agent and edges toward filler, keeping it out of the top band.

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 create/mutation tool with no output schema, the definition should at least say what a profile represents, what a successful creation returns or enables, and any preconditions. None of that is present, leaving the agent to rely entirely on the schema and annotations.

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 schema already documents name, number_id, and the response_format enum; the description supplies no additional parameter meaning. Per the baseline rule for fully covered schemas, a 3 is the appropriate ceiling.

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 verb+resource ("creates a new profile for a number") is identifiable, but it is a near-verbatim restatement of the title and adds no elaboration on what a number profile actually contains or how it differs from siblings like placetel_activate_number_profile or placetel_delete_number_profile. An agent must infer the concept of a 'profile' from the sibling list.

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 versus placetel_list_number_profiles, placetel_activate_number_profile, or placetel_activate_number, and no stated prerequisites (e.g., whether the number must exist or be activated first). The only contextual cue is the raw POST path, which the agent must decode itself.

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