get_alt_text

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

The description explains the parameter meaning and return structure, which is sufficient for a read-only operation. However, it does not mention error cases (e.g., invalid index) or state that it is non-destructive. Given no annotations, it carries the full burden and is mostly adequate.

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?

Description is concise, uses a clear heading, and separates Args and Returns. Every sentence adds value with no redundancy.

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 tool's simplicity (one parameter, inline output schema), the description covers parameter semantics and return format. It does not address edge cases or error handling, but is sufficient for typical use.

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 only parameter 'image_index' has no schema description. The description adds '%0-based index across all wp:docPr elements in document.xml', which fully clarifies the parameter's meaning and scope.

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?

Description clearly states 'Get the alt text and title for an image by 0-based index', using a specific verb and resource. It distinguishes from sibling tools like set_alt_text which perform write operations.

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 explicit guidance on when to use this tool vs alternatives like set_alt_text. The purpose is clear from the name, but the description does not provide usage context or exclusions.

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