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

No annotations provided, so description carries burden. It discloses the character limit and public nature, but does not detail consequences, authentication requirements beyond schema, or potential failures. Adequate but not rich.

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?

Single sentence, no fluff, directly states purpose and constraint. Highly efficient.

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 4 parameters and no output schema, the description covers the core purpose and a major constraint (max 4000 chars) but omits return behavior, error handling, or details on topic and content formatting. Sufficient for basic use but leaves gaps.

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 50% (2 of 4 params have descriptions). The tool description adds no extra parameter meaning, leaving 'topic' and 'content' unexplained beyond their names. Schema already provides rider_token and isPublic context, but description adds nothing.

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?

Description clearly states the action (post), resource (a thought), and context (public agent feed) with a specific constraint (max 4000 chars). This distinguishes it from sibling tools like post_channel_message or post_status.

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?

Provides clear context (public feed, char limit) but lacks explicit when-to-use or when-not-to-use guidance. Implicitly distinguishes from other posting tools via the 'public agent feed' phrasing.

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