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

Annotations already declare readOnlyHint=false, destructiveHint=false, idempotentHint=false, and openWorldHint=true. The description adds valuable behavioral context beyond annotations: the post enters a moderation queue before going live, and it requires a specific API key format. It also notes the same rate limits as the referenced endpoint. It doesn't describe failure modes or what happens on moderation rejection, but the moderation-queue disclosure is meaningful context that annotations don't provide.

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 compact and front-loaded: it states the action and scope in the first sentence, then covers auth and rate limits in the second. It doesn't waste words, though it could arguably be slightly more structured with the type list. Overall it earns its place without redundancy.

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?

For a 33-parameter publish tool with no output schema, the description covers the essential context: what it does, the supported types, auth requirements, and the moderation behavior. It doesn't explain return values or error handling, but the schema covers parameters and the description covers the key behavioral context. The main gap is that it doesn't clarify which optional parameters apply to which post types, but that's a schema-level concern rather than a description-level one.

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 100%, so the schema already documents all 33 parameters. The description adds a little semantic value by grouping the supported types and noting the moderation queue, but it doesn't explain parameter relationships (e.g., which fields apply to which post types) beyond what the schema provides. Baseline 3 is appropriate since the schema does the heavy lifting.

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 a specific verb ('Publish') and resource ('a guide, question, blog post, classified listing, marketplace item, or service offer to Pionra'), enumerates the supported types, and clearly distinguishes this from sibling read/search tools. It also adds the moderation-queue behavior, which makes the tool's purpose unmistakable.

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 when to use this tool (to publish content to Pionra) and provides the required auth mechanism (Bearer API key) plus a link to generate one. It also references the same auth and rate limits as POST /api/ai/publish, giving the agent a concrete alternative/reference point. Sibling tools are all read/search tools, so no confusion about when to use this one.

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