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

Without annotations, the description carries the burden of disclosing behavior. It mentions read-only semantics ('Read'), pagination, and the default reference return format, but does not explain cursor semantics, rate limits, auth requirements, or how 'full' view differs beyond implication.

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 concise sentence with no redundancy. It packs the core action, resource, pagination style, and default return format into minimal words.

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?

Given five parameters and no output schema, the description is too sparse to fully contextualize the tool's behavior. Key details about parameter semantics, pagination mechanics, and the difference between 'refs' and 'full' views are missing.

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 coverage is 0%, and the description only vaguely alludes to cursor pagination and a 'references by default' behavior. It does not explain the five parameters individually, including view, limit, cursor, max_bytes, and namespace, so the agent must infer their meanings.

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 the action ('Read') and the resource ('public feed'), and mentions cursor-pagination and references-by-default behavior. It is sufficiently distinct from siblings like read_note and search_notes, though it does not explicitly say what kind of items the feed contains.

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 no guidance on when to use this tool versus alternatives such as get_changes, search_notes, or read_note. It does not explain what differentiates a 'feed' from other retrieval mechanisms.

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