ppt_read

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

No annotations exist, so the description must disclose behavioral traits. It fails to explain how the file is determined (e.g., active presentation, file picker), what exactly text content includes (all slides? notes?), or any side effects. For a tool with no parameters, this is critical missing info.

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, clear sentence. While concise, it could benefit from adding one more sentence about file selection without becoming wordy. No unnecessary information.

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 no output schema and no annotations, the description should explain at least the source of the file (e.g., active window, target parameter) and the scope of text. It completely omits this, making it incomplete for proper usage.

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?

There are no parameters, so the schema requires no explanation. The description adds purpose to the text content extraction but doesn't clarify how the file is selected, which is a minor gap. Baseline 4 given zero parameters.

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 specifies the action (reads), resource (slide text content), and file type (.pptx). It distinguishes from siblings like ppt_create (create) and pdf_read (different format).

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 on when to use this tool vs alternatives. No conditions, prerequisites, or context about file selection are mentioned. The agent is left uninformed about how to invoke it correctly.

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