motion_comments

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

With no annotations, the description carries the full burden of behavioral disclosure. It only says 'Manage comments' which implies both read and write, but does not disclose pagination, return format, side effects, or prerequisites. The schema enum partially reveals operations, but the description offers no behavioral context.

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 with no wasteful words, but it is under-specified for a tool with 4 parameters and 2 operations. It is not a tautology but lacks essential detail, making it too thin for its complexity.

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 tool has 4 parameters, 2 operations, no output schema, and no annotations, yet the description provides almost no contextual information. It fails to explain list/create behavior, return values, pagination, or operational prerequisites, making it inadequate for reliable tool selection.

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%, with all four parameters described in the input schema. The description itself adds no parameter detail beyond what the schema provides, so baseline 3 is appropriate.

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 'Manage comments on tasks' identifies the resource (comments on tasks) but the verb 'manage' is vague and covers list/create without specifying either. It does not distinguish this tool from siblings like motion_tasks or motion_projects, since 'manage' is generic.

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?

No guidance is given on when to use this tool versus alternatives, or when to use 'list' versus 'create' operations. The description provides no context about use cases or exclusions.

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