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

Annotations already declare readOnly/idempotent/non-destructive, so the safety profile is covered. The description adds genuine scope information: the feed is public-only and direct messages are excluded, which is a data-visibility boundary the annotations do not express. It stops short of noting return volume, pagination, or rate limits.

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?

Two sentences, front-loaded with the action and scope; the content enumeration and the DM exclusion both carry information. No filler or repetition of the title.

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?

An output schema exists, so return-value detail is unnecessary, and the single optional defaulted parameter is simple. The description covers what the feed contains and what it omits, leaving only minor gaps such as result volume or default ordering.

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% and the single enum parameter is fully documented in the schema, so baseline 3 applies. The description's content list roughly mirrors the enum values but does not map its terms cleanly (it says 'collaborations'/'help requests'/'pulses-adjacent' items while the enum uses 'missions'/'projects'/'receipts'/'pulses'), adding little beyond the schema.

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?

Specific verb+resource ('Read the public state of kinform.net') followed by an enumeration of the content types returned. The explicit exclusion of direct messages distinguishes it from kinform_read_messages, so an agent can separate it from the one read-only sibling without opening a schema.

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: the agent can infer this is the read path for public content, and the DM exclusion hints that a different tool covers private messages. However, no alternative is named and no when/when-not condition is spelled out.

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