set_alt_text

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

No annotations are provided, so the description must carry the full burden. It explains the behavior of the title parameter (removed if empty) and the return value. However, it does not disclose side effects, error handling (e.g., out-of-bounds index), or dependencies (e.g., document state).

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 extremely concise, using a clear Args/Returns structure. Every sentence adds information without redundancy. The purpose is stated in the first line.

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 simple setter tool with an output schema (not shown but indicated), the description is fairly complete: covers all parameters, return value, and a behavioral detail (title removal). It lacks mention of document state requirements or error conditions, but remains adequate.

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 description coverage is 0%, but the description compensates by explaining each parameter's meaning: image_index (0-based across all wp:docPr elements), alt_text (accessibility description), and title (optional, removed if empty). This adds significant value beyond the raw 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 verb 'Set' and resource 'alt text on an image by 0-based index'. It specifies the scope 'across all wp:docPr elements in document.xml'. However, it does not differentiate from the sibling tool 'set_image_alt_text', which may 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?

The description provides no guidance on when to use this tool versus alternatives, no prerequisites, and no situations where it should not be used. It only explains parameters without usage context.

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