get_blend_track_assignments

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

Annotations already indicate readOnlyHint, destructiveHint=false, and idempotentHint=true. The description adds value by detailing the return format (child, index, edges) and the GUID constraint, without contradicting annotations.

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 well-structured and concise, opening with a clear purpose, followed by parameter details and a structured explanation of the return value. Every sentence adds value without redundancy.

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 simple resource (one parameter, read-only), the description fully covers the input constraint, parameter, and output structure. No output schema exists, so the detailed return format is essential and provided. No gaps for this 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?

With 0% schema description coverage, the description provides a clear explanation for the single parameter blend_track_guid, including an example GUID. This fully compensates for the lack of schema descriptions.

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 explicitly states it retrieves a list of assignments for a Blend Track, including child GUIDs, index, and edge configs. While the name already identifies the resource, it does not explicitly differentiate from similar sibling tools like get_switch_container_assignments, but the focus on Blend Tracks is clear.

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 says 'Only accepts GUIDs' and implies usage for inspecting assignments, but lacks explicit guidance on when to use this tool versus alternatives (e.g., get_switch_container_assignments) or when not to use it.

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