request_publish_prompt_snippet

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

With no annotations, the description carries the full burden of behavioral disclosure. It mentions that the tool creates a pending approval requiring human approval and returns the pending approval with readiness. However, it omits prerequisites (e.g., user permissions, snippet existence, or behavior if a pending request already exists).

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 two sentences long, front-loads the core purpose, and wastes no words. All information is relevant and concisely stated.

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 no output schema, the description notes that the tool returns the pending approval with readiness, which is sufficient. It also covers the essential behavior. However, it does not address error conditions (e.g., invalid id or duplicate request), which slightly reduces completeness.

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 input schema already documents both parameters with descriptions. The tool description does not add any additional meaning beyond what the schema provides, resulting in a baseline score of 3.

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 'request' and the resource 'prompt_snippet be published'. It further clarifies that the action does not publish but creates a pending approval, distinguishing it from a direct publish action. The resource name also differentiates it from sibling tools targeting other resources.

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 usage when initiating a publish request for a prompt snippet and clarifies that it does not publish immediately. However, it does not explicitly state when not to use this tool, nor does it provide alternatives (e.g., if the snippet is already pending approval or if another tool should be used for direct publishing).

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