muse_publish_document

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

With no annotations, the description carries full burden for behavioral disclosure. It only states the action (publish) but omits details like whether it creates or updates, authentication requirements, rate limits, or handling of failures. This lack of transparency is a significant gap for a tool interacting with external APIs.

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, clear sentence that front-loads the core purpose. It is efficient, though slightly oversimplified, and could benefit from a brief note on when to use or a reference to the schema for details.

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 tool's complexity (multiple platforms, nested options, no output schema), the description lacks crucial context such as return values, error handling, prerequisites, or authentication setup. It is inadequate for an agent to fully understand the tool's behavior and expected outcomes.

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?

The description adds minimal value beyond the input schema. The schema already provides descriptions for all parameters, including nested options, and the enum list for platform. The description merely echoes the platforms without clarifying parameter usage or providing additional context.

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 states the verb 'Publishes' and the resource 'generated documents', listing all six target platforms. It effectively differentiates from sibling tools, which are mostly analysis and generation tools, making the tool's purpose unambiguous.

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 implies use when you need to publish a document to an external platform, and the sibling tools are distinct enough not to cause confusion. However, it does not explicitly mention when not to use it or provide alternatives.

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