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 of disclosing behavioral traits. 'Get' implies a read operation, but the description does not explicitly state it is non-mutating or safe, nor does it mention authentication, rate limits, error cases, or pagination. The only added behavioral detail is that all slide data is included, which is minimal.

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, front-loaded sentence that immediately communicates the main purpose. Every word contributes: 'Get', the resource type, synonyms, 'by ID', and the inclusion of all slide data. No verbosity or 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?

For a simple tool with one parameter and no output schema, the description gives the core purpose and a hint of the return content ('all slide data'). However, it omits important context such as the shape of the returned data, any prerequisites, and how it relates to sibling tools. Since there is no output schema, the description should provide a bit more detail to be fully self-sufficient.

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 100% with the parameter 'id' described as 'Presentation ID'. The description's 'by ID' adds no new meaning beyond the schema. According to the rubric, with high schema coverage the baseline is 3, and there is no additional value to raise the score.

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 'Get' and the resource 'slide presentation', with synonyms (slides, powerpoint, deck, keynote) to disambiguate. The phrase 'by ID' specifies the lookup mechanism and 'including all slide data' defines the scope, distinguishing it from sibling tools like get_document or get_sheet.

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?

There is no guidance on when to use this tool versus alternatives such as list_slides or get_document. The description does not mention prerequisites (e.g., need to obtain the ID via a list operation) or any exclusions, so the agent receives no decision support for tool selection.

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