get_channel_digest

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

Annotations already declare readOnlyHint=true, so description does not need to repeat safety. Description adds that it summarizes activity, which is core behavior, but lacks details on output format or edge cases (empty channel). Adequate but not rich.

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?

Single sentence, no wasted words. Front-loaded with verb and resource. Perfectly sized for the complexity.

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?

Given complexity (2 params, read-only) and presence of output schema, description covers main purpose and parameter semantics adequately. Could add more on when to use, but overall sufficient for a simple summarization tool.

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 coverage is 0%, so description must compensate. Description links 'N hours' to 'hours' parameter and 'channel' to the required parameter, but does not explain default values, constraints (e.g., maximum 168), or channel format. Partially clarifies but not fully.

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 uses specific verb 'Summarise' and identifies resource 'channel activity', specifying included items (active users, threads, files). Distinguishes from sibling tools like get_channel_info or get_channel_messages.

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?

Implies usage for summarizing recent activity but does not explicitly state when to use versus alternatives (e.g., get_channel_info for metadata, search_messages for detailed search). No when-not or exclusion criteria.

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