send_sticker

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

With no annotations, the description carries the full burden of disclosing behavior. 'Send sticker message' only implies a write operation but does not mention side effects, permissions, reversibility, or response expectations. This is a significant gap for a mutation tool.

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?

While the description is short, it is under-specified rather than appropriately concise. Four words do not provide sufficient information for a tool with 5 parameters, and the single sentence fails to earn its place beyond being a bare restatement of the name.

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 complexity (5 parameters, no annotations, no output schema), this description is completely inadequate. It does not explain what a sticker message is, when to use it, or any parameter semantics, making it impossible for an agent to invoke the tool correctly without external knowledge.

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% and the description does not mention any of the 5 parameters (link, phone, chatId, mediaId, quotedMsgId). The description adds no meaning to the parameters, leaving the agent without any clues about their purpose or required formats.

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 'Send sticker message' simply restates the tool name 'send_sticker' without adding any new information about what a sticker message is or how it differs from other send tools. It is a tautology that fails to distinguish this tool from siblings like send_message or send_file.

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. With many sibling send tools (send_button, send_carousel, send_contact, etc.), the description offers no contextual clues or exclusions, leaving the agent without direction on selection.

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