Get a keyword automation

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds one piece of behavioral context beyond that: the response includes whether the automation is still waiting for the next post (nextPostStatus). It says nothing about error behavior for an unknown/invalid id or the rest of the returned shape.

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?

One sentence with zero filler, front-loading the verb and resource and appending the most notable returned field. Nothing to remove.

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 single-parameter read tool with a full annotation safety profile and no output schema, the description covers what it does and highlights a key returned field. Slightly richer return-value context would be needed for a 5 given the lack of an output schema.

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% and the single 'id' parameter is documented as the keyword publicId with UUID format. The description's 'by its publicId' simply echoes the schema, adding no format, lookup, or failure semantics beyond it. Baseline 3 applies when the schema does the heavy lifting.

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?

States a specific verb and resource ('Get one keyword automation') and explicitly scopes it to a single item, which implicitly separates it from the sibling list_keywords. It stops short of explicitly naming or contrasting with list_keywords, so it is clear but not maximally differentiated.

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 phrase 'by its publicId' implies you must already know the identifier, which hints at when this is appropriate versus a list call, but the description never states when to use this instead of list_keywords or what to do if the id is unknown. Usage is only implied.

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