flowforge_manage_phone_pools

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

Annotations already declare destructiveHint=true, readOnlyHint=false, openWorldHint=true and idempotentHint=false, so the safety profile is covered. The description adds the campaign-attachment behavior, which is real context beyond annotations, but it does not warn that destructive actions share the same entry point as reads, nor mention the confirm gating or irreversibility of delete/remove_member.

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?

Two short sentences: the action surface is front-loaded in a single dense clause, and the follow-up sentence carries the only cross-tool relationship worth stating. There is no filler or repetition of the title.

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?

An output schema exists, so return values need not be described, and the description covers the action surface plus the campaign linkage. The residual gap is that a nine-action, partly destructive tool does not flag that most actions require pool_id or that delete/remove_member need explicit confirmation, though the schema does supply those.

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?

Reported schema description coverage is 0% for the top-level params wrapper, so the description is expected to carry meaning about inputs. It names the operations but says nothing about the parameters that drive them — fields, weight, priority, confirm, pool_id, phone_number_id — leaving the agent to infer all of that from nested $defs.

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 opens with a precise, enumerated verb+resource list (list/create/update/delete phone pools, add/remove members, peek next number, read statistics) that tells an agent exactly what domain the tool governs. It falls short of a 5 because the enumerated actions omit 'get' from the PoolAction enum, and it never distinguishes itself from adjacent siblings such as flowforge_manage_phone_number or flowforge_list_phone_numbers.

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?

It gives one genuinely useful cross-tool instruction: attach a pool to a campaign via flowforge_update_campaign_settings with phone_pool_id to rotate caller ID. However, it offers no guidance on when to choose this tool over flowforge_manage_phone_number versus flowforge_list_phone_numbers, and no guidance on which action to pick for a given intent beyond the action verb list.

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