get_slide_transition

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

No annotations are provided, so the description carries full burden for behavioral disclosure. It only states what it gets, but does not mention what happens if no transition is set, whether the operation is read-only, or any potential side effects. For a read operation, more clarity on default values or null returns would be beneficial.

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, well-structured sentence that directly states the tool's functionality. No wasted words or 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 the tool has one parameter and no output schema, the description provides a basic understanding but lacks detail on the return format (e.g., object structure) and edge cases. For a simple getter, it is marginally adequate but not thorough.

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 100% (slideIndex with min and description). The description adds no additional meaning beyond what the schema already provides. Baseline score of 3 applies as the schema does the heavy lifting.

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 ('Gets'), the resource ('current transition effect, duration, and delay'), and the target ('for a slide'). It distinguishes from sibling tools like 'set_slide_transition' and 'list_transition_types' by focusing on retrieval of specific properties.

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 implies usage for reading existing transition settings, but it does not explicitly state when to use this tool versus alternatives like 'set_slide_transition' or provide any prerequisites or context (e.g., slide must have a transition). No when-not or alternative guidance is given.

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