Workspace summary (account, signer, follow-ups, paths)

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

No annotations provided, so description bears full burden. It lists output fields but does not disclose behavioral traits like read-only nature, authentication requirements, side effects, or whether it makes network calls. A read status tool should explicitly state it is safe and non-destructive.

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?

Two sentences: first enumerates output fields, second gives usage advice. No fluff, all sentences add value. Front-loaded with what it does, then when to use it. Appropriate length for a simple status tool.

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?

The tool has two optional parameters and no output schema. Description lists output fields but does not explain how parameters affect output, return format, or any constraints. For a status tool that can be filtered by account or chat scope, this omission leaves the agent guessing about parameter effects and response structure.

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 tool description does not explain either parameter (accountAlias, chatScope). The listed output fields (e.g., 'account connection') hint at accountAlias role, but no explicit mapping or usage guidance. Description adds no value beyond schema for parameter understanding.

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 explicitly states what the tool shows (account connection, signer, inbox batch, follow-ups, paths) and suggests it as a first step. Title reinforces 'Workspace summary'. Distinguishes from sibling tools which are specific actions, making it clear this is an overview tool.

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?

Description says 'Use this first when unsure what to do next', providing clear context and a usage condition. However, it does not explicitly state when not to use it or mention alternatives, though the context of many siblings implies it is a starting point.

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