tokportal_rewarm_account

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

Annotations indicate readOnlyHint=false (suggesting mutation) and destructiveHint=false, which fits the 'starts session' action. The description discloses behavioral traits like 3-day split, non-expiry of tasks, and verification before payment, which are beyond annotations. However, it could mention if rewarming affects existing bundle state or is reversible, but overall strong.

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 detailed but a bit dense, using multiple sentences to convey important nuances. It front-loads the main action and then lists conditions and behavior. Could be slightly more concise by grouping related constraints, but every sentence adds value.

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?

Given the complexity of the tool (3 parameters, 100% schema coverage, no output schema), the description is highly complete. It explains the entire workflow, prerequisites, credit cost, scheduling, and verification. No output schema is needed as the tool likely just starts a session; the description covers return behavior adequately.

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%, but the description adds context beyond the schema: it explains the rate calculation, the 3-day task scheduling, that earlier-day tasks remain available, and that sessions with tasks do not expire. This helps the agent understand the parameter semantics more fully than the schema alone.

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 clearly states it orders Advanced Niche Warming (rewarm) on a delivered account, with a specific verb 'Order' and resource 'Advanced Niche Warming'. It distinguishes from siblings like tokportal_generate_warming_terms or tokportal_list_account_warming_sessions by focusing on initiating a new session.

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 provides explicit prerequisites: requires active TokPortal Coverage, a routable active account manager with non-cancelled support order, TikTok or Instagram platform, and no already-active warming session. It also explains the credit rate and how to get effective rate via GET /credit-costs, guiding when to check costs.

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