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

Adds real context beyond annotations: the marketplace listing is the public contract while deployments stay private, paid listings force code protection, and re-publishing updates the existing listing rather than duplicating. The idempotency statement aligns with idempotentHint=true, and no permissions or rate-limit behavior is described.

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?

Five short sentences, each carrying distinct information, with the core purpose front-loaded and the sibling redirect placed last where it is found when needed. No filler or restatement of the title.

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 an 8-parameter mutation with annotations and no output schema, the description covers visibility consequences, idempotent re-publish behavior, pricing modes, and the private alternative. Gaps are minor: no mention of what the returned listing contains or required account/ownership prerequisites for accountId.

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 cross-parameter meaning the schema alone doesn't state clearly — that tags are for categorization (holdingPeriod, riskLevel, plan tier) and that choosing a paid listing forces code protection — which helps an agent reason about interacting fields.

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?

Specific verb+resource+scope: 'Publishes a strategy to the public marketplace where users can discover it.' The second sentence draws a precise boundary between the public marketplace listing and private bot deployments, which separates it from sibling tools like start_deployment and save_marketplace_publication.

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?

Names an explicit alternative and the condition that selects it: 'For private 1:1 sharing, use strategy_share_link(action="create") instead.' It also clarifies the already-published case (updates and returns the existing listing). It does not cover publish preconditions or how it relates to unpublish/remove siblings, so not a full 5.

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