CPA: chat by actionId

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

Adds 'Read-only, spends no money' and rate limit beyond annotations, which already mark it as read-only, nondestructive, idempotent, and open-world.

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?

Three concise sentences front-load the purpose, then add behavioral and usage info without any unnecessary words.

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?

Covers purpose, usage, behavior, and rate limit; lacks output structure description but given low complexity and single required parameter, it is adequately complete.

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 coverage is 100% with parameter description; description reinforces that actionId is obtained from cpa_chats_by_time_v2, adding contextual value.

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?

Description uses specific verb 'Returns' with resource 'CPA chat model' by actionId, clearly distinguishing it from siblings like cpa_chats_by_time_v2 that iterate by time.

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?

Explicitly states when to use (when you have actionId from cpa_chats_by_time_v2) and when not (not for iterating), plus rate limit of 3 requests/min.

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