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

The annotations declare readOnlyHint:true, but the description repeatedly states 'THIS CALL PUBLISHES THE DECISION' and 'calling this marks THIS decision publicly readable at its card URL.' This is a direct contradiction between the structured annotation and the described side effect, so behavioral transparency scores 1 per the rubric.

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?

The description is substantive but front-loaded, beginning with what the tool returns and immediately flagging the publish side effect. The privacy section earns its place because it clarifies exactly what becomes public, and the workflow line is a compact routing instruction.

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?

The description covers return shape, platform options, privacy boundaries, and the intended workflow, which is strong for a publication tool. It stops short of a perfect score because caller_id is undocumented and the exact platform character limits are not stated, though an output schema exists to carry return details.

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?

With 0% schema description coverage, the description must carry parameter meaning, and it does add value for platform ('x | farcaster | generic') and include_rationale ('journal body unless include_rationale=true'). However, caller_id is never explained, and wallet_address/decision_id are only inferable from context, leaving gaps for a tool with five parameters.

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 names a specific action and resource: it produces a pre-filled, ready-to-publish post for a journal card and returns a platform-specific share payload. It also differentiates itself from the sibling get_journal_card by noting it returns the same card plus the share payload and that review alone publishes nothing.

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 context is explicit: 'Workflow: SHARE step -- get_journal_card to review, this to publish' and 'Reviewing with get_journal_card publishes nothing.' This tells an agent exactly when to call this tool versus the review tool and warns that this call has publish side effects.

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