element_read

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

The readOnlyHint=true annotation already establishes this is a safe, non-mutating read, so the description need not restate that. It does add value by scoping the payload to 'details and formatting properties', but says nothing about whether the response includes raw formatting structures, inheritance from theme/master, or whether the element must exist on the given slide.

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?

A single, front-loaded sentence with no filler or redundant restatement of the name. Every word ('details', 'formatting properties', 'single') contributes 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?

The tool is simple (three required IDs, fully documented) and read-only, so the bar is low. However, with no output schema, the description is the only source of information about the return shape, and 'details and formatting properties' is too terse to tell an agent what fields to expect.

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%, with all three UUID parameters individually documented, so the schema carries the semantics. The description adds nothing about ID scoping or what happens if slideId and elementId are inconsistent, which is the baseline expectation when the schema is already complete.

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?

States a specific verb ('Read') and a specific resource ('details and formatting properties of a single element on a slide'). The word 'single' implicitly contrasts with the sibling element_list, but no sibling is named explicitly, so differentiation is only partial.

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?

Usage is only implied: the three required identifiers suggest the caller must already know deckId/slideId/elementId, and 'single element' hints this is for targeted lookups rather than enumeration. There is no explicit when-to-use, no mention of when to prefer element_list, and no note on error behavior for unknown IDs.

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