send_animation

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

Annotations already declare readOnlyHint=false, openWorldHint=true, idempotentHint=false and destructiveHint=false, so the safety profile is covered. The description adds only a format constraint and says nothing about delivery semantics, whether the media must be re-uploadable by file_id, or what happens on failure — nothing beyond what the structured fields already convey.

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?

One front-loaded sentence with no filler, and the format constraint is placed where it is most useful. It is efficient, though its brevity borders on under-specification rather than true concision given the surface area of the tool.

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?

For a 23-parameter, non-idempotent send operation with no output schema and weak schema coverage, this description is far too thin. An agent gets no information about caption limits, spoiler behavior, notification suppression, or business-connection scoping.

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?

With 23 parameters and only 43% schema description coverage, the description needs to compensate and does not. The only value it adds is constraining the 'animation' parameter's accepted formats; width, height, duration, spoiler, paid-broadcast, and thread parameters get no explanation anywhere.

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 gives a specific verb (Send) plus resource (animation) and defines the accepted media as GIF or soundless H.264/MPEG-4 AVC video. That definition implicitly separates it from send_video, though it never names that sibling explicitly.

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?

There is no explicit when-to-use or when-not-to-use guidance. The format parenthetical hints that silent video belongs here rather than in send_video, but the agent must infer that routing decision instead of being told it.

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