list_keywords

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

The description says 'Extract,' implying a read operation, but does not disclose behavioral traits such as side effects, error cases (e.g., missing filepath), or whether the operation is safe (no annotations provided). The agent lacks crucial 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 sentence, which is concise and front-loaded. However, it is slightly too sparse, trading brevity for completeness.

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 lack of output schema and the tool's integration into a complex video editing server, the description is insufficient. It does not clarify the type or scope of keywords/tags, nor the expected return format, leaving substantial gaps for an agent.

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 has 0% description coverage, and the tool description does not explain the parameter 'filepath' (e.g., what it refers to, expected format). The description adds no meaning beyond the parameter name, leaving ambiguity.

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 specifies a verb ('Extract') and a resource ('all keywords/tags from project'), making the tool's function clear. It also distinguishes from sibling tools like list_clips or list_markers, which serve different purposes.

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 provided on when to use this tool versus alternatives. The description lacks context for typical use cases, prerequisites, or conditions that would help an agent decide when to invoke this tool.

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