get_broadcast_snapshot_by_ids

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

The description adds value beyond annotations by noting that the tool uses a POST method that returns data, does not change account records, and may create a short-lived cached result-set. This aligns with the readOnlyHint and idempotentHint annotations, providing useful context about its behavior.

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 concise and front-loaded with the purpose. It uses a clear header line with emoji and method, followed by a simple explanation. No wasted sentences.

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 there is no output schema, the description does not explain what the snapshot contains, which could be important for the agent. It mentions the caching behavior but lacks details on the return value structure.

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?

The description adds meaning to the 'body' parameter by stating it expects 'specified broadcast IDs'. The schema lacks a description for the 'ids' property, so the description compensates. However, it does not clarify the format or constraints beyond what the schema provides.

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's purpose: 'Get broadcast snapshot' and 'Returns snapshot for specified broadcast IDs'. It specifies the verb ('Get') and resource ('broadcast snapshot'). However, it does not explicitly differentiate from sibling tools like 'get_broadcast_snapshot' or 'get_broadcast_metrics', which could cause confusion.

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 is provided on when to use this tool versus alternatives, such as get_broadcast_snapshot or get_broadcast_metrics. There is no mention of prerequisites, exclusions, or context.

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