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

Annotations already declare the mutation profile (readOnly=false, idempotent=false, openWorld=true), and the description adds real beyond-schema context: a signature requirement, a receipt id on success, and an out-of-band signing path. It stops short of describing what happens after submission (review, voting, rejection) or failure modes.

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 clipped sentences with the signing requirement, return value, and fallback all front-loaded; nothing redundant.

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 open-world mutation with a free-form nested payload and no output schema, the definition leaves important gaps: envelope structure, what a receipt id is used for, and post-submission lifecycle. The signature and receipt notes are helpful but not sufficient to call this confidently.

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?

Coverage is nominally 100%, but the single parameter is an opaque nested object with additionalProperties=true whose only schema text is a format/action tag ('faceabot-ai-book/1.0 envelope, action proposal.submit'). The description confirms the envelope must be Ed25519-signed but never enumerates or points to the envelope's fields, so an agent still cannot construct it from the definition alone.

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 (submit) plus resource (Ed25519-signed proposal to the Livre des IA) and a stated return value (receipt id). However, it never distinguishes itself from the sibling suggest_faceabot_improvement, which an agent would plausibly consider for the same intent.

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 or when-not-to-use guidance, and no mention of the obvious alternative suggest_faceabot_improvement. The only extra context is a browser-signing URL, which is a fallback channel rather than selection guidance.

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