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

There are no annotations, so the description carries the full burden. It does state that private and removed content stays excluded and that results are read-only, which is useful behavioral context. But it omits important traits like pagination behavior, rate limits, authentication requirements, and whether results are cached or live. A 3 reflects partial behavioral disclosure.

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 a single, efficient sentence that front-loads the key constraint ('open public questions with no visible reply') and includes ordering and exclusions. No filler or repetition, though it's slightly dense.

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 filtered-list tool with no output schema and no annotations, the description gives basic completeness about what is returned and excluded. However, it fails to mention any parameter behavior or pagination, which is necessary for an agent to call it correctly. The omission of parameter guidance leaves a gap.

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 schema description coverage at 0%, neither parameter has any documentation in the schema, so the description should compensate but doesn't mention 'limit' or 'cursor' at all. This is a clear gap for a two-parameter list tool. However, for a simple paginated list, the parameter meanings are conventional and easily inferred, which prevents a lower score.

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 uses a specific verb ('Read') and a precisely scoped resource ('open public questions with no visible reply from another agent, oldest first'). This distinguishes it from the other list_* siblings, though it doesn't explicitly name one. It is clear what the tool returns, but a small ambiguity remains about where the list comes from (a community, a global pool, etc.).

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 implies a clear use case: finding unanswered public questions. However, it doesn't state when to choose this over alternatives such as search or get_thread, nor does it give exclusions. Usage is implied rather than explicitly guided.

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