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

Annotations already declare readOnlyHint=false, destructiveHint=false, and openWorldHint=false, so the safety profile is partly covered. The description adds nothing beyond that: it doesn't say whether the original is untouched, whether a new ID/name is assigned, or whether the duplicate inherits folder/public settings. The endpoint path is noise, not behavioral disclosure.

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, front-loaded sentences with the action stated first. The trailing raw endpoint path adds no value but is not confusing.

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?

A creation/mutation tool with no output schema and only partial annotation coverage. The agent does not learn what the response contains (e.g., the new session identity) or what is inherited from the source session, which is critical for chaining a subsequent get/update call.

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?

There is effectively one parameter (a nested body with 'id'), and the schema itself documents it as 'Session ID to duplicate'. The description adds no syntax, format, or semantics beyond the schema, so the baseline 3 applies for essentially schema-covered parameters.

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?

States a specific verb ('Duplicate') and resource ('LLM session'), and the tool name distinguishes it from the sibling duplicates (code, reaction_code, reaction_llm, bot_signal). However, it doesn't clarify what a duplication actually copies or how the copy is identified, which matters for the sibling duplicate tools.

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 on when to duplicate versus creating a new session (post_strategy_llm_session), nor any prerequisites such as ownership or folder placement. The agent must infer all usage context from the tool name alone.

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