manage_slide_masters

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

Annotations provide no readOnly or destructive hints, so the description bears the full burden. It says 'Access and manage' yet all listed operations ('list', 'get_layouts', 'get_info') are read-only, which is mildly misleading. There is no disclosure of side effects, persistence, error behavior, or what 'manage' actually mutates.

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 compact and well-organised with an Args/Returns structure, making key parameter information scannable. It earns its sentences, though 'Access and manage' is slightly vague and somewhat redundant given the operation list.

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 description provides enough parameter detail to attempt an invocation, and since an output schema exists, the return-value outline is sufficient. However, it lacks per-operation semantics (what 'list' versus 'get_info' actually returns), does not clarify which operation uses layout_index, and offers no fallback/error context for missing presentation_id. Overall it is minimally viable but with clear gaps.

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 compensates by explaining every parameter with useful details: operation values are enumerated, indexes are specified as 0-based, and presentation_id is described as optional with a fallback. This is meaningful beyond the raw schema, though it does not map each parameter to specific operations.

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 identifies the resource — slide master properties and layouts — and lists three concrete operation values ('list', 'get_layouts', 'get_info'), so the agent knows what the tool does. However, it does not explicitly distinguish this from sibling tools like get_template_info or list_slide_templates, relying on the resource name to differentiate.

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 vs alternatives such as list_slide_templates, get_template_info, or apply_specific_template. The operation list implies some usage scenarios, but the description does not state exclusions, preconditions, or preferred context, leaving the agent to infer when this tool should be selected.

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