get_presentation_info

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

The annotations already provide readOnlyHint=true, so the read-only nature is covered. The description adds no behavioral context beyond that, such as how a null presentation_id is handled or whether the tool operates on the current presentation. It essentially restates the tool's purpose without revealing any additional behavior.

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 short sentence with no filler, so it is concise. However, the brevity sacrifices substance: it almost parrots the tool name and provides no distinguishing or operational detail. It is acceptable as a minimal description but not well-structured for decision-making.

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?

While an output schema exists and the readOnlyHint annotation covers safety, the description is too incomplete for an agent to confidently invoke the tool. The key ambiguity of presentation_id being optional—and whether 'a presentation' means the current one or one to be identified—is unresolved. Given the large sibling set, this lack of context makes tool selection harder.

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%, so the description needed to clarify the presentation_id parameter's meaning and optionality. It does not mention the parameter at all. The schema's title 'Presentation Id' and default null provide minimal information, but the description adds no value beyond that.

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 states a clear verb and resource: 'get information about a presentation.' However, it does not specify what kind of information is returned, and it does not distinguish this tool from similar getter siblings like get_slide_info or get_template_file_info.

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 about when to use this tool instead of the many sibling getters, nor whether presentation_id is required, optional, or refers to the currently open presentation. The agent is left to infer usage from the tool name alone.

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