get_broadcast_snapshot

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint. Description adds 'Fetches data. Makes no changes' which confirms but does not add new behavioral context beyond annotations. No mention of pagination, rate limits, or snapshot contents.

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?

Description is concise with minimal repetition, but the emoji/HTTP line and separate 'Get broadcast snapshot' line could be merged. Still efficient and front-loaded.

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?

Despite having good schema coverage and annotations, the description lacks explanation of what a 'snapshot' entails and does not differentiate from other broadcast retrieval tools (e.g., get_broadcast_snapshot_by_ids, get_broadcast_metrics). Missing output schema increases need for description completeness.

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 100%, so parameters are fully documented in the schema. Description does not elaborate on parameters or provide additional context beyond what the schema already provides. Baseline 3 is appropriate.

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 clearly states it retrieves broadcast snapshot data for all broadcasts, with specific HTTP method and path. Distinguishes from siblings like get_broadcast_snapshot_by_ids by implying it returns all broadcasts rather than filtered by IDs.

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?

No guidance on when to use this tool versus alternatives like get_broadcast, get_broadcast_metrics, or get_broadcast_snapshot_by_ids. Only states it fetches data without changes, but does not specify context or exclusions.

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