Share Dashboard

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

Discloses the behavioral trait that the public link resolves without a passphrase by default, adding value beyond annotations (which only indicate idempotentHint and destructiveHint). Does not mention potential side effects if sharing is already enabled, but overall informative.

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?

Two sentences: first describes action and output, second provides a crucial warning. No wasted words; front-loaded with the primary action.

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?

With a single parameter and an output schema available, the description fully covers the tool's purpose, output, and a key behavioral note. It is complete for the tool's simplicity.

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 100%, so the baseline is 3. The description adds minimal clarification ('business id') beyond the schema description, so no extra value.

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?

Clearly states the tool enables public sharing for a dashboard and returns a share token and embed id. It is distinct from sibling tools like create_dashboard or get_dashboard, focusing specifically on sharing.

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?

Provides context for when to use (enable public sharing) and includes a warning about the default lack of passphrase, implying caution. However, it does not explicitly state when not to use or suggest alternatives.

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