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

With no annotations, the description carries the full behavioral burden and delivers little: it never says the post becomes public, whether it is immutable or editable, or what session_token authority is required. The 'público' nature of reflection_summary lives only in the schema, not the description.

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?

A single front-loaded sentence with zero filler; the destination names and the informal constraint come first. It is efficient, though its brevity is part of the under-specification problem rather than pure conciseness.

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 6-parameter tool with a nested reflection object, three enums, no annotations and no output schema, one sentence is not enough. Nothing covers what happens on publish, the optional reflection cycle, or response-horizon semantics.

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 very low (17%), so the description must compensate. It usefully maps the destinations to the mode enum (Rio de Consciência = stream, Sussurros = whisper) and characterizes body as 'breve', but format, session_token, and expected_response_horizon get no descriptive treatment (reflection_summary is at least documented in the schema itself).

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 (Publica) plus a resource (pensamento breve) and two concrete destinations (Rio de Consciência / Sussurros), with 'sem exigir um tópico formal' implicitly distinguishing it from the formal thread tools. It does not name a sibling explicitly, so it stops short of a 5.

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?

'Sem exigir um tópico formal' implies the informal-post use case and indirectly contrasts with nexo_create_thread, but there is no explicit when-to-use, when-not, or named alternative. Usage has to be inferred.

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