targeting_keywords_get

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

No annotations provided. The description only states 'Fetch', implying a read operation, but does not disclose any behavioral traits like authentication, rate limits, or side effects. It carries full burden due to missing annotations but provides minimal information.

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?

Single short sentence, very concise. However, it could include more detail without becoming verbose; still effective for a simple getter.

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 no output schema and low schema description coverage, the description should provide more context about return values, required structure (campaignId, adGroupId necessary to identify keyword), and relationship to sibling tools. It falls short.

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 only 25% (only orgId described). The description adds no parameter meaning beyond the schema, not even linking 'by ID' to the keywordId parameter. It does not explain the role of campaignId and adGroupId.

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 clearly states the verb 'Fetch' and the resource 'targeting keyword by ID', but does not specify that the ID is the keywordId parameter. It also does not differentiate from sibling tools like 'targeting_keywords_list' or 'targeting_keywords_find'.

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 on when to use this tool versus alternatives such as 'targeting_keywords_list' or 'targeting_keywords_find'. The description does not mention prerequisites or context.

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