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

Annotations already declare readOnlyHint=true, openWorldHint=false, and destructiveHint=false, so safety is covered. The description adds only that results are constrained to Share Build candidates; it says nothing about result volume, ordering, or whether a missing vehicleId means 'all'.

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?

A single front-loaded sentence with zero filler; the scope qualifier ('for Share Build') does the work of distinguishing this from the many other list_* tools.

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 a full output schema present, return values need not be explained, and the one optional parameter is documented. The main gap is the missing link to the preview_share_build/send_share_build siblings that consume this output.

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% and vehicleId's own description already explains it narrows setup/session options. The description adds no syntax, format, or default-behavior detail beyond the schema, so baseline 3 applies.

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 (Lists) and concrete resources (TuneWorks vehicles, setups, and sessions) scoped to 'Share Build'. This differentiates it from generic list_vehicles/list_setups/list_sessions by the Share Build filter, but it never names those siblings explicitly.

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 phrase 'available for Share Build' implies the tool is a prerequisite step for preview_share_build/send_share_build, but there is no explicit when-to-use, when-not-to-use, or named alternative. Usage must be inferred from the workflow.

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