get_slides_mode

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

No annotations are provided, so the description carries the full burden for behavioral disclosure. The description indicates it is a read operation ('Get') and states deprecation, implying it may be removed or unsupported. It does not describe side effects or permissions, but for a simple getter the behavioral insight is sufficient.

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 extremely concise with a single informative sentence plus a deprecation warning. The '[DEPRECATED]' tag is front-loaded, instantly informing the agent. No redundant words; every part adds value.

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 no parameters and no output schema, the description adequately covers functionality and deprecation. However, it could improve by briefly describing the return format (e.g., 'returns a string mode'), but the deprecation makes this less critical.

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 tool has no parameters (100% schema coverage by default), so the description does not need to add parameter meaning. Baseline score of 4 applies for zero-parameter tools.

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 tool's purpose: getting the current viewport mode in Figma Slides. It distinguishes itself from sibling tools by explicitly declaring deprecation and recommending 'get_current_context' as a replacement, providing unambiguous purpose differentiation.

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 explicitly warns that the tool is deprecated and instructs the agent to use 'get_current_context' instead. This provides clear when-to-use and when-not-to-use guidance, with a direct alternative named.

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