telegram_briefing

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

No annotations are provided, so the description must carry the burden. It describes the tool as collecting and returning data, implying a read-only operation, but does not explicitly state whether it has side effects or requires permissions. The behavioral traits are adequately implied but not fully explicit.

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 somewhat lengthy and includes instructions that could be condensed. It front-loads the trigger phrases but repeats the _playbook and telegram_send_me instructions. Adequate but not optimally concise.

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 the presence of an output schema (unshown), the description explains the two data categories and next steps (send via telegram_send_me). It is complete for a composite tool, though it could mention how hours affects the output.

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%, but the description thoroughly explains the 'hours' parameter: its meaning (aggregation time range), recommendation for morning (12 hours), and default value. This adds significant meaning beyond the schema.

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 clearly states the tool aggregates Telegram mention data for market briefings, listing two specific output categories (trending and momentum) and distinguishing itself from siblings like telegram_trending and telegram_momentum. It also provides trigger phrases for usage.

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 explicitly states when to call this tool (for specific briefing queries) and instructs the agent to use telegram_send_me afterwards. It provides clear context but does not explicitly list when not to use it.

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