flowforge_manage_phone_number

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

The annotations only flag destructiveHint=true and readOnlyHint=false, which is coarse for a tool that also performs pure reads. The description earns credit for disclosing the dry-run gating mechanism, the monetary cost of purchase, and the fact that release is irreversible-adjacent - all behavior not present in the annotations. It does not describe pagination or what the dry-run response contains, but the output schema covers returns.

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 sentences, zero filler, and the most consequential constraint (dry run unless confirm=true) is placed where it will be read. The capability list is front-loaded ahead of the safety caveat, which is the correct ordering for a multi-action tool.

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?

With an output schema present, return values need not be explained, and the annotations already carry the safety profile. The description fills the remaining gaps that matter for correct invocation: per-action scope, the cost-bearing purchase, and the confirm gate on the destructive paths.

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 reported top-level schema coverage is 0%, but the nested ManagePhoneNumberInput properties each carry detailed descriptions (action semantics, confirm requirement, E.164 source, country_code example). The description's main added value is the confirm/dry-run workflow, which is already stated in the schema's confirm description, so it largely reinforces rather than extends the 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 opens with a specific enumeration of verbs and the exact resource: 'Read, rename, buy or release one phone number; list supported countries and area codes.' The 'one phone number' scoping implicitly separates it from flowforge_list_phone_numbers and flowforge_search_phone_numbers, though neither sibling is named, so an agent must infer the boundary rather than being told.

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 a strong, actionable operating rule: purchase and release are dry runs until confirm=true, and the agent must confirm the number and cost with the user first. What is missing is routing guidance against the nearby siblings (list/search/assign phone numbers), so the when-to-use-this-vs-alternative dimension is left implicit.

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