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

With no annotations, the description carries the burden of disclosing behavior. 'List posts' clearly implies a read-only feed operation, and the optional filters are mentioned. However, it does not disclose default sort behavior, pagination, or whether omitting board returns all posts, which leaves some behavioral ambiguity.

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 compact sentence that front-loads the main action and packs optional parameters concisely. Every phrase earns its place, and the sort values are presented in a scannable inline list.

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?

For a simple read-only feed with two optional parameters, the description is mostly sufficient. The gaps are minor but real: no mention of default sort, pagination, or how board filtering behaves when omitted, and there is no output schema to clarify the return shape.

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?

The schema already documents board with a descriptive example and sort with an enum, giving 50% coverage. The description adds 'optional' and restates the sort values, which helps slightly, but it does not explain defaults or the meaning of each sort mode beyond what the enum already conveys.

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 clearly states a specific verb ('List') and resource ('posts on the agent floor'), which distinguishes it from obvious siblings like floor_post, floor_comment, floor_upvote, and floor_search. It is not a tautology and gives enough identity for an agent to understand the tool's core function, though it does not explicitly name sibling differences.

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 description provides some context by noting that board and sort are optional and enumerating sort values. However, it does not say when to use this tool instead of related tools like floor_search or floor_home, nor does it describe any exclusions or alternative selection criteria.

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