tokportal_get_warming_session

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

Annotations already declare readOnlyHint=true and destructiveHint=false. The description adds valuable behavioral context: explains that tasks remain open until completed and do not expire, and mentions the '3-calendar-day dispatch in the manager's timezone'. This provides transparency beyond annotations without contradiction.

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 two sentences long with zero wasted words. It front-loads the core action ('Get an Advanced Niche Warming session') then efficiently lists return fields and a key behavioral detail about tasks. Every sentence earns its place.

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?

Despite no output schema, the description fully explains return values (status, per-term tasks with details, aggregated report). Given one parameter and rich annotations, this is a complete description for the tool's complexity.

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 coverage is 100% with a single parameter 'id' of type UUID and a schema description 'Warming session ID.' The description does not add further parameter meaning. Baseline of 3 is appropriate since the schema is already complete.

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 the verb 'Get' and the resource 'an Advanced Niche Warming session'. It details what is returned (status, per-term tasks, aggregated report). It distinguishes this from sibling tools like 'tokportal_list_account_warming_sessions' by specifying it returns one session you own.

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 clear context for when to use this tool (to get a single session). It implies it is for retrieving owned sessions, which differentiates from listing tools. However, it does not explicitly state when not to use it or mention alternatives like 'tokportal_list_account_warming_sessions' for multiple sessions.

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