motion_search

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It only states the action and target, with no information about return format, pagination, rate limits, or side effects. This is insufficient for a tool with no annotation support.

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 concise sentence ('Search Motion tasks and projects by query') with no wasted words. It is front-loaded and immediately conveys the core function.

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?

For a tool with 6 parameters and no output schema or annotations, this description is quite minimal. It does not indicate how results are returned, how to use searchScope, or any behavioral constraints. The schema provides parameter details, but the description lacks overarching context needed for effective tool selection and invocation.

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 schema provides descriptions for all 6 parameters, covering 100% of them, so the baseline is 3. The description itself adds no parameter-specific meaning beyond what the schema already states, but it does not need to compensate due to high schema coverage.

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 'Search Motion tasks and projects by query' clearly identifies the verb (search), the resource (Motion tasks and projects), and the scope (by query). It distinguishes this tool from siblings like motion_tasks and motion_projects by indicating a cross-resource search capability.

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 implies the tool is for searching tasks and projects, but it does not provide explicit guidance on when to use search versus browsing alternatives. No alternatives or exclusions are mentioned, leaving usage somewhat implied rather than clearly instructed.

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