Create a plotting task from explicit headless selections

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

The annotations already mark the tool read-only and idempotent; the description adds concrete exclusions ('does not preview, materialize, execute code, or install dependencies') and the cached-result-set requirement. This goes beyond the annotations without contradicting them.

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?

Three sentences, each earning its place: context and function, key constraint, and explicit non-effects. It is front-loaded and has no filler.

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?

The main flow and safety profile are clear, but with no output schema the return contract is unstated, and the description doesn't say where resultSetId comes from. It is adequate for selecting the right tool, less complete for confidently invoking it with well-formed selections.

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 0%, so the description must carry parameter meaning, but it only addresses the constraint on selections ('Selections must belong to the current cached result set') and never explains resultSetId, providerId, or exactSelector semantics. This is insufficient for a two-required-parameter tool with nested selection objects.

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 names a specific verb and resource ('Create the same v2 plotting-task handoff') and clearly positions it for an agent-only session with explicit headless selections. It also differentiates from preview/materialize/execute behaviors, though it doesn't name a sibling.

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 clear context: use after the user selects candidates in an agent-only session, constrained to the current cached result set. It does not explicitly name alternative tools or when-not-to-use conditions, but the intended context is evident.

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