get_chat

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

Annotations already show safety (readOnly, idempotent). The description adds context about local cache and offline operation, which is beyond annotations and helpful for understanding staleness.

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 concise sentence with critical behavioral context front-loaded. No wasted 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?

For a simple read tool with robust annotations and a clear sibling set, the description is adequate. It could mention return format, but not necessary given the tool's simplicity.

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 50% (only chat_jid described). The tool description does not add any information about parameters, leaving include_last_message's behavior unexplained.

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 action ('Get') and resource ('WhatsApp chat metadata by JID'), distinguishing it from siblings like 'list_chats' which lists all chats.

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?

It implies offline usage via 'reads local cache; works while disconnected' but does not explicitly state when to use versus alternatives (e.g., for real-time data), nor does it provide exclusions.

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