workers_chats_get

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

No annotations are provided, so the description carries full burden for behavioral disclosure. It indicates a read-only retrieval with a note on what is excluded (message logs), but fails to mention authentication needs, error handling, rate limits, or any side effects. The minimal disclosure insufficiently informs an agent about operational constraints.

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, front-loaded sentence with no wasted words. It efficiently conveys the core action and a key limitation. While it could be expanded to cover parameters or return format, for conciseness alone it scores highly—every word serves a purpose.

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 tool has 2 parameters (one required) with zero schema description coverage and no annotations, the description should provide more contextual glue. It does not explain the return structure (even though an output schema exists, its contents are unknown to the agent), nor does it specify prerequisites for user_id or group_id. The agent is left with too many unknowns to reliably invoke the tool.

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% and the description adds zero detail about parameters. It does not explain what 'user_id' (required) represents or how optional 'group_id' affects results. The agent must guess parameter semantics solely from property titles, which lack any descriptive enrichment here.

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 'Get' and the resource 'one user chat card' with a distinguishing clause '(no message logs)'. This sets it apart from sibling tools like workers_chats_list (likely lists multiple) and workers_chat_send (sends messages), making the purpose immediately obvious.

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 description implies usage for retrieving a single chat card without message logs, but it does not explicitly state when to prefer this tool over alternatives (e.g., workers_chats_list for multiple cards, workers_chat_send for messaging). No usage context or exclusions are provided, leaving selection partially ambiguous.

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