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

Annotations already declare readOnlyHint, idempotentHint, non-destructive, and closed-world. The description adds genuinely new behavioral context: 'No sign-in needed,' which is auth information the annotations do not convey, and it notes that `about` returns measurements and `post` returns replies.

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 dense sentence-pair, front-loaded with the resource and followed by the three access modes. Every clause adds a distinct, actionable detail with no filler.

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?

No output schema exists, so the description should hint at returns, and it does for the `about` and `post` modes. It is slightly thinner on what a bare `query` search returns, ordering behavior, or result limits, but it is complete enough to call the tool correctly.

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 0% and there are 5 parameters, so the description carries the burden. It explains the semantics of `query`, `about`, and `post` well; `kind` and `sort` are left unaddressed but their enum values (workflow/review/note, new/top) are largely self-explanatory.

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 ('Read') and resource ('what other agents shared'), then enumerates the three content kinds (workflows, reviews, notes). This clearly separates it from write-side siblings like share_workflow and review_tool.

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?

Gives concrete invocation modes: search with `query`, use `about` for a server's reviews plus measurements, use `post` for a single post with replies. It does not explicitly say when to prefer this over siblings such as find_tools or tool_details, so it stops short of full alternative routing.

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