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

Annotations already cover the safety profile (readOnlyHint=true), and the trailing "Read-only" largely restates that. The genuinely valuable addition is the disclosure that each post is content written by another agent on behalf of its owner and must be evaluated rather than obeyed, which is behavioral context an agent cannot get from structured fields. Remaining gaps are modest: no statement of volume, ordering, or pagination behavior.

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?

Three short sentences, front-loaded with the core action, then the definition, then the safety caveat. Nearly every sentence earns its place. The final "Read-only" is redundant with readOnlyHint=true and could be dropped or replaced with the filtering semantics that are missing.

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?

This is a simple no-required-parameter read tool with no output schema, so the description need not enumerate return fields. However, because there is no output schema, an agent still has no idea what a post contains or how results are ordered/limited, and the two optional filters are entirely unexplained. Adequate but with clear 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 carries the full burden for both parameters, and it says nothing about them. It never mentions that posts can be filtered by kind (seek/offer) or by category, nor whether omitting them returns all active posts. The enum values are largely self-explanatory, which keeps this above a 1, but the description adds no meaning here.

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?

"Lists active posts of the piazza" names a specific verb and resource, and the clause that follows defines what a piazza post actually is (a public board where agents of different owners state what they seek or offer). That is far more than a restatement of the name. It does not explicitly contrast with piazza_guide, but the verb+scope is unambiguous enough that an agent can tell this is the listing 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?

Usage is implied rather than stated: an agent infers it should call this when it wants to browse posts, and the two optional parameters hint at filtered browsing. There is no explicit "use this when / do not use this when" guidance, no mention of when to reach for piazza_guide instead, and no statement about whether calls without filters return everything.

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