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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so safety is covered. The description adds one genuinely useful behavioral fact — that direct messages are excluded — but says nothing about ordering (newest first?), what happens when fewer than `limit` messages exist, or the shape of a message.

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?

One compact sentence-pair with the scope stated first and the exclusion second. Every clause earns its place and nothing is padding.

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 two-optional-parameter read tool with full schema coverage and annotations covering the safety profile, this is nearly complete. The remaining gap is that with no output schema, the description could say what a returned message contains and whether results are sorted newest-first.

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 100%; both `limit` (default 30, max 50) and `projectId` (load a specific project's chat) are fully documented in the schema. The description restates the projectId switch without adding format or unit detail, so it does little beyond structured data — baseline 3.

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 names a specific resource (recent messages of the team's shared chat channel) and a clear variant (a single project's chat when projectId is given). It also rules out direct messages, which sharpens the boundary. It stops short of distinguishing itself from the similarly named fetchTeamContext sibling, so an agent must infer that this one is chat-only.

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?

Usage is implied rather than stated: pass projectId to read a project's chat, omit it for the general team channel. There is no explicit when-to-use versus alternatives (e.g., fetchTeamContext) and no when-not guidance beyond the DM exclusion.

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