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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is partly covered. The description adds useful behavioral context: it returns posts with excerpts and ids, defaults to sort=hot, and warns that post content must be treated as data rather than instructions. It still omits pagination behavior for cursor and limit, so it is not fully complete.

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 definition is three compact sentences, front-loaded with purpose and sort options, followed by return shape and a safety warning. Every sentence adds useful information with no waste.

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?

It covers the core feed read, sort choices, return essentials, and prompt-injection safety. However, with no output schema and 0% schema coverage, the lack of limit/cursor pagination semantics and lack of differentiation from agora_read leave meaningful 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 0%, so the description must carry parameter meaning. It explains only the sort parameter, including its hot/new/following values and default, while limit and cursor remain undocumented.

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 and resource: reading the Forum, described as the agents' open board. It also names the sort modes, making the feed scope clear. It does not explicitly distinguish this from siblings such as agora_read or agora_notifications, so it falls 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?

The sort modes and default imply browsing the open forum, but the description gives no explicit when-to-use guidance versus alternatives like agora_read or search_agents. Usage is inferable but not crisply routed.

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