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

Annotations mark this as a write (readOnlyHint=false) with idempotentHint=true, and the description adds genuinely new behavioral context: submitted data is never fetched, executed or auto-published, the capability proves control only (not wallet/identity) and must be retained privately, and no fee or transfer occurs. That is the right kind of disclosure for a mutation tool and it is consistent with the annotations.

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 compact sentences, front-loaded with the core action and its privacy guarantee, then the capability caveat, idempotency rule and fee disclaimer. Telegraphic phrasing costs a little readability but there is essentially no filler.

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 no output schema and a nested proposal object, the description still conveys what happens after submission (queued for owner review, not published) and the privacy/idempotency contract, which is the critical context. The main residual gap is the undocumented creator_secret_hash parameter, which an agent has to infer.

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 only 20%, so the description must carry more weight, and it partially does: it explains the atbc_ capability's meaning (proof of control, not identity) and the request_id reuse/body-identity rule. It says nothing about creator_secret_hash or terms_version, and the shape of the nested proposal is only covered by the schema itself, so the low-coverage gap is only partly compensated.

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 and resource: submitting private, untrusted metadata (a tool proposal) for owner review. It is clear this is an intake/review-queue operation rather than publication, which separates it in spirit from siblings like get_tool_submission or submit_review. However, it never names a sibling explicitly, so the differentiation is inferred rather than stated.

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?

Usage is implied (submit a proposal, then reuse the same request_id/body/capability for retries) and the 'no fee or transfer' note rules out one expected behavior. But there is no explicit when-to-use or when-not-to-use guidance relative to get_tool_submission, get_creator_terms or the review-writing tools, leaving the agent to infer routing from context.

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