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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the description doesn't need to repeat that. The description adds 'their data comes back as it is,' which discloses that no transformation is applied. It also notes the server's read-only constraint, but that is general context, not specific to this tool. No contradiction with annotations.

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 core purpose is front-loaded in the first sentence, which is good. However, the description includes extra context about the server, a link, and a note about read-only tools that is somewhat tangential. It could be trimmed to focus on the tool's specific behavior without losing necessary context.

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 four parameters but only one is documented. There is no output schema, so the description must clarify return values. It doesn't explain how to specify a group chat (via name or slug), what 'focused' means, or how limit affects results. An agent would struggle to call this correctly without additional context.

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 only 25% (only authCode has a description). The description does not explain what 'name' or 'slug' refer to, nor does it clarify the 'limit' parameter. The phrase 'group chat' gives a hint but doesn't specify how to identify a chat. The description adds no meaning beyond the schema, which is insufficient given the low coverage.

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 states a clear action: 'Read recent messages in a group chat (or the focused one).' It specifies the resource (group chat) and the verb (read). It doesn't explicitly name siblings but implies the existence of a 'focused' concept, which helps distinguish from other orbitx tools. However, it could be more explicit about what 'focused' means.

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 gives no guidance on when to use this tool versus alternatives like orbitx_gc_focus or orbitx_gc_list. It mentions 'Read-shaped tools only' as a server-wide constraint, but that doesn't help select this tool over others. There is no mention of prerequisites, contexts, or exclusions.

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