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

Adds substantial context beyond the annotations: auth requirements, the verified-backlink prerequisite, the non-publishing nature, and the dedup nuance that repeated pending normalized URLs are acknowledged without overwriting (refining the idempotentHint=false signal). The outcome_unknown recovery instruction is behavior an agent could not infer from annotations alone.

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?

Front-loads the prerequisites, then purpose, then caveats, then the recovery step, in five tight sentences with no filler. It is dense but appropriately sized for the complexity; minor cost is that constraints and purpose are interleaved rather than cleanly grouped.

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 an output schema present, return values need no explanation, and annotations cover the safety profile; the description fills the gaps that matter (auth, backlink, non-publishing, dedup, retry). The remaining hole is parameter-level detail for name/officialUrl/details, which neither schema nor description supplies.

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 0%, so the description carries the full burden. It adds real meaning for two parameters (email must match the verified account; images are uploaded separately via authenticated HTTP), but name, officialUrl, description, and the entire nested details object remain wholly undocumented.

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?

States a specific verb and resource ('Submit an app or personal agent') plus the decisive scope ('for private operator review... Does not publish'), which separates it from any publish flow. It also names the sibling to consult on an ambiguous outcome ('inspect list_my_submissions'), so an agent can route correctly without opening other schemas.

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?

Gives concrete preconditions (email OTP auth, verified root homepage backlink, email must match the account) and an explicit fallback path for outcome_unknown. It stops short of stating when NOT to use this tool versus siblings like verify_homepage_backlink or compare_tools, but the operational guidance is unusually clear.

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