Share Presentation

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

The description openly discloses that no sharing/permissions endpoint exists and the tool is not wired up. This is valuable behavioral context beyond any annotations, effectively warning the agent that calls will fail.

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 that directly communicates the non-implementation status. It is concise and front-loaded with the key warning.

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 that the tool is a stub, the description adequately conveys it should not be used. It doesn't explain intended behavior or error handling, but for an unimplemented tool, this is sufficient.

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%, and the description provides no information about presentationId or access parameters. The agent must rely solely on the schema, which lacks explanations.

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 states 'Not implemented' rather than describing what the tool does. It provides no verb or resource, only a negative status. The title implies sharing, but the description does not confirm any actual functionality.

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 states the tool is not implemented, making it clear it should not be used. This provides a strong when-not guideline, even though no alternative tools are mentioned.

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