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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, covering the safety profile. The description adds the notion of 'privacy-filtered project metadata', which hints at some filtering behavior, but it is vague and does not explain what gets filtered, under what conditions, or what the tool returns (e.g., empty result vs error). For a read-only tool with annotations, this is still a thin addition.

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 sentence, so it is concise in length, but it is poorly structured. The phrase 'hosted get' is redundant and confusing, and the sentence does not front-load the most critical information (what the tool returns or when to use it). It reads like an auto-generated or truncated description, not a carefully crafted one.

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 0% schema coverage and lack of an output schema, the description must carry substantial explanatory weight. Instead, it provides almost nothing: no return format, no parameter meaning, no usage context, no differentiation from siblings. The tool is effectively unusable for an agent without external knowledge.

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 coverage is 0% and the description mentions no parameters. The 5 parameters (projectId, requestId, sessionId, executionId, presentationId) have no explanatory text anywhere. The description fails to compensate for the complete lack of schema documentation, leaving agents guessing what values to provide and why.

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 uses the verb 'Read' and identifies the resource as 'presentation authoring brief', which is a specific artifact distinct from generic presentations. However, the phrase 'hosted get presentation authoring brief' is malformed ('hosted get' is redundant and likely a typo), and there is no explanation of what an 'authoring brief' is or how it differs from sibling tools like get_presentation or presentation_read.

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 provides no guidance on when to use this tool versus alternatives. It does not mention prerequisites, conditions, or exclusions. An agent has no basis to choose this over get_presentation, list_presentations, or presentation_read, all of which read presentation-related data.

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