chat_get_cockpit_overview

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

No annotations are provided, so the description carries the behavioral disclosure burden. It clearly states 'It only reads local JSON files,' which establishes a read-only, non-mutating safety profile. It also names the local data sources aggregated in the packet. It omits error/rate-limit behavior, but the key safety-relevant behavior is disclosed.

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 front-loaded with the tool's purpose, followed by a compact list of packet contents, a read-only guarantee, a knowledge-base reference, and a concrete example. Each part earns its place, though the KB pointer is less universally useful than the rest.

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 output schema covers return shape, and the description explains what data is aggregated and that the operation is local/read-only. It is missing parameter semantics and sibling-tool routing, but with three optional parameters and an example, an agent can still invoke the tool reasonably. The lack of guidance on when to use it versus chat_get_cockpit_ledger_detail is a notable gap.

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%, so the description must compensate. Only the `session` parameter is illustrated via the example call, and `limit` and `message_limit` are never semantically explained. The parameter names and defaults give some hints, but the description does not adequately define what they control or how they interact.

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 opens with a specific verb and resource: 'Return a display-ready MCP Chat cockpit overview packet.' It also enumerates the packet's contents, making the tool's function clear. It does not explicitly differentiate from sibling tools like chat_get_cockpit_ledger_detail, though the 'overview' vs 'ledger detail' contrast is implied.

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 through 'cockpit overview' and 'display-ready packet,' and it notes the tool only reads local JSON files. However, it never explicitly states when to prefer this over chat_list_sessions, chat_get_session_resume_context, or chat_get_cockpit_ledger_detail, nor does it provide any when-not-to-use guidance.

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