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

readOnlyHint already establishes that the call is non-mutating, and the description is consistent with it. Beyond that annotation, it adds site scoping and recency but does not disclose ordering, how “recent” is determined, or empty-result 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?

Two short sentences front-load the operation and then provide the recommended workflow, with no boilerplate or repetition. The wording is compact, although “notes/context” is slightly imprecise.

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 read this explains why the tool exists, but not enough to invoke it confidently because all three inputs are undocumented and there is no output schema. It should at least clarify site selection, limit behavior, and what determines recency or result 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 coverage is 0%, and the description does not directly document limit, domain, or site_id. “For the site” weakly hints that domain or site_id selects a site, but leaves their differences, whether they are alternatives, defaults, and the effect of limit unresolved.

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 and resource—“Get recent notes/context”—and scopes them to “the site,” so the basic operation is clear. It does not explicitly distinguish this recent-collection read from siblings such as get_note or get_ai_context.

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?

“Recommended before creating tweets/posts” gives a concrete workflow point when the tool should be called. It does not explain when notes are unnecessary or route agents to alternatives, but the primary use case is explicit.

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