skylight_set_message_caption

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

Without annotations, the description should disclose behavioral traits. It states only the action, not effects, permissions, error conditions, or idempotency. This is risky for an agent invoking a mutation.

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 a brief 5-word sentence, achieving conciseness but at the expense of providing any additional guidance. It is not front-loaded with any extra information beyond the tool 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?

The description covers only the basic action without the necessary context for an AI agent to correctly invoke this tool. It lacks parameter details, return value info, and behavioral expectations, making it inadequate.

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 provides no information about the three parameters. With 0% schema coverage, the agent must guess the meaning of 'id', 'caption', and 'frameId' from names alone. This inadequately guides parameter selection and formatting.

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 uses a specific verb ('Set') and identifies the resource ('message/photo caption'), clarifying that it can set captions on both messages and photos. While somewhat brief, it adequately distinguishes from sibling tools like skylight_add_message_comment (which adds a comment) or skylight_get_message (which retrieves). It could be more specific about context.

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 provides no guidance on when to use this tool versus alternatives, no prerequisites, and no exclusions. The agent is left to infer usage context from the tool name alone, which is insufficient.

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