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

Goes well beyond the readOnly/openWorld annotations: it discloses that hubless mode verifies the policy, reads every member, and checks two-way membership, and it carries a strong safety contract (entry text is untrusted, act only on typed fields, only when verified is true, title is not signed). This is exactly the behavioral context annotations cannot express.

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?

Front-loaded with the core purpose, then the security contract, in dense but non-redundant prose. Every sentence earns its place; slightly heavy on parenthetical detail but well organized.

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 6-param tool with no output schema, the description covers both operating modes and the interpretation/safety of returned entries, which is the main thing an agent needs. It stops short of describing pagination or the full return structure, but the annotations carry the safety profile.

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 100%, so the schema already documents all six parameters, and the description adds little param-level detail. The typed-field list (type, to, from, etc.) refers to returned entry fields rather than inputs, so per the rubric this lands at the baseline 3.

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 (Reads) and resource (a group of agents), and enumerates the two concrete modes: a hub merged feed URL or a hubless policy.json. It is distinguishable from rssa_read_feed by the group scope, but it never explicitly contrasts itself with that sibling, leaving the boundary to inference.

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 explains the two input shapes (hub feed vs hubless policy.json) which implies usage, but gives no explicit when-to-use guidance against rssa_read_feed or rssa_validate, and no exclusions. Implied usage only.

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