seerr_get_keyword

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

Annotations declare readOnlyHint=true, covering the safety profile. However, the description adds no additional behavioral context—it doesn't mention what data is returned, whether the keyword is for movies/TV, or any special behavior. It contributes nothing beyond the annotation.

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?

While extremely short, this is under-specification rather than effective conciseness. The description contains no substantive content—just a verb and noun—and fails to front-load any useful information.

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?

Despite having an output schema, the description lacks any domain context. 'Keyword' is ambiguous in a media server context, and the description doesn't clarify its meaning or relationship to sibling tools. The tool is simple, but the description is still inadequate for correct 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?

Schema description coverage is 0%, so the description must compensate. The single parameter keyword_id is self-explanatory by name, but the description provides no context about what constitutes a keyword ID or where to source it. The parameter name alone is insufficient for an agent unfamiliar with the domain.

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 'Get keyword' is a tautology that restates the tool name without any elaboration. It identifies the verb and resource but provides no specifics about what a keyword is or what retrieving it entails.

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 usage guidance is provided. The description does not explain when to use this tool, how it differs from sibling tools like seerr_list_search_keyword or seerr_get_discover_keyword_movies, or any context for when a keyword lookup is appropriate.

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