set_alt_text

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

No annotations are present, so the description carries the burden. It reveals the underlying write target (general.altText) but does not disclose potential side effects, permissions needed, or whether it overwrites existing alt text.

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 single, focused sentence that front-loads the main action and adds a useful technical detail. No wasted words.

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 straightforward setter with clear schema coverage, the description adequately explains what the tool does and where it writes. It could mention overwrite behavior or prerequisites, but the simplicity of the operation makes it reasonably complete.

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 75%, with descriptions for page, visual, and text. The description adds context for the 'text' parameter by linking it to the altText property, but does not otherwise enhance parameter understanding beyond the schema.

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 function: setting a visual's accessibility alt text, with the specific target property (singleVisual.objects.general.altText). It distinguishes itself from sibling set_* tools by focusing on alt text for screen readers.

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 context of use is implied: use for setting alt text for accessibility. However, it does not explicitly mention when to choose this over other tools or any exclusions, so guidance is minimal.

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