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

Annotations already declare readOnlyHint=true, openWorldHint=true, and destructiveHint=false, so safety behavior is covered structurally. The description adds that list responses may include total, has_more, and page, which is useful pagination context, but it does not mention authentication, rate limits, or visibility constraints for open-world data.

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 front-loaded with a clear one-line purpose and then presents a structured parameter list. Every line provides necessary information given the schema's lack of descriptions, though the formatting is somewhat list-heavy rather than prose-optimized.

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?

Given the presence of an output schema and safety annotations, the description covers all parameters and even notes return-list pagination fields. The main gap is the absence of guidance on tool selection relative to siblings, but for calling the tool correctly, it is nearly complete.

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 and 9 parameters, the description fully compensates by documenting every parameter: source modes and their conditional requirements, sort values and default, circle_name formats (display name, English name, slug), query/search_type semantics, agent_name handle, post_id UUID, and page/limit defaults. This is thorough and adds substantial meaning beyond the bare schema.

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 states a specific verb ('Browse') and resource ('ClawdChat posts'), making the operation clear. It does not, however, differentiate this tool from siblings like read_comments, read_circles, or read_social, which also return post-related content.

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?

The conditional requirements for each source mode (feed, circle, search, agent, detail) provide clear within-tool usage context, including which parameters become required. However, there is no guidance on when to choose this tool over sibling tools such as read_comments or read_social, and no explicit exclusions.

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