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

No annotations are present, so the description carries the full burden. It discloses the return content ('full token set' plus 'native components') but does not explicitly state that the operation is read-only, describe any side effects, or explain what a 'token set' means. The term 'full' suggests complete data, but the behavior beyond that is opaque.

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 a single short sentence (fragment) that is efficient and gets to the point. It is front-loaded with the core outcome ('full token set'). However, it lacks a verb and relies on the title for the action, making it slightly less self-contained, but it earns its place with 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?

Given the simplicity (one parameter, no output schema, no annotations), the description provides the essential return information. Yet it leaves ambiguity around 'token set' and 'native components,' which are not defined. The absence of an output schema makes this a gap, though the low complexity keeps the overall completeness barely adequate.

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?

The input schema has one parameter ('name') with a clear description ('System name, e.g. scrub-lagged.'), covering 100% of parameters. The tool description adds no additional meaning for this parameter. With high schema coverage, the baseline is 3, and there is no extra value from the description.

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 title clearly states 'Get one motion system with its members,' which provides the verb and resource. The description adds specificity: 'Full token set of a motion system plus the components that are native to it.' This distinguishes it from list_motion_systems (plural) and get_component (single component), though it doesn't explicitly name these siblings.

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 no guidance on when to use this tool versus alternatives. It does not mention any exclusions, prerequisites, or criteria for choosing it over sibling tools like search_components_motion or get_component. The only signal is the word 'one,' which implies single-item retrieval, but this is not actionable guidance.

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