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

Annotations declare a non-idempotent, non-destructive write, so mutation is at least signaled structurally. The description adds nothing beyond that: it doesn't mention that submission triggers policy analysis, creates a review-queue item, populates analytics/author history, or any side effects around doNotStore.

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?

Two words is not conciseness but under-specification; there is no structure, no front-loaded purpose, and nothing that earns or justifies the omission.

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 deeply nested moderation-submission tool with 30+ policy variants, a clientAction recommendation system, and no output schema, a two-word description is completely inadequate; an agent cannot confidently call this correctly from the description alone.

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?

The single top-level `request` parameter has zero description coverage and the description says nothing about its structure, the required body/content shape, project scoping, or the policy override option. The nested schema fields do carry descriptions, but the composite request envelope – the main thing an agent must construct – is undocumented and unmitigated by the description.

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?

"Submit content" restates the tool name with no added specificity – it never says the content is sent for moderation, that a moderation result/review-queue item is produced, or how it differs from siblings like content-allow and content-reject.

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?

No when-to-use, when-not-to-use, or alternative guidance of any kind. An agent has no way to know whether to call this versus content-allow/content-reject or the queue tools.

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