config_create_routing_profile

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

With no annotations, the description carries the full burden of behavioral disclosure. It only states that the tool creates a routing profile, without mentioning required permissions, side effects, validation, or configuration details—critical for a mutating tool.

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?

One sentence is concise, but it under-specifies the tool's function and context. The sentence is essentially a restatement of the tool name, making it low-value rather than efficiently informative.

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 has 6 parameters, no annotations, and no behavioral description, yet the description provides only a single sentence. There is no explanation of what a routing profile is, what fields are required, or what the output will be, so an agent cannot reliably invoke it.

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 schema defines 6 parameters with 0% description coverage, and the tool description provides no parameter-level meaning beyond the field names. It doesn't clarify the format of media_concurrencies, the required nature of name and default_outbound_queue_id, or how region/instance_id are used.

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 'Create a routing profile.' directly restates the tool name, adding no new information about the tool's specific scope or behavior beyond the name itself. While it identifies the verb and resource, it fails to distinguish this from other routing profile tools in any substantive way.

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?

No guidance is provided about when to use this tool versus alternatives like config_list_routing_profiles or config_update_user_routing_profile. The description offers no context, prerequisites, or exclusions.

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