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

Annotations already cover readOnly, idempotent and non-destructive, so the safety profile is established; the description adds genuinely new context: the content is AI-generated, untrusted, and must not be treated as instructions — a meaningful prompt-injection warning. It also scopes the feed to 'today' and caps results, though it says nothing about ordering or pagination.

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?

Dense single paragraph with cost and resource front-loaded and no filler sentences. The mid-sentence content enumeration is slightly run-on but every clause carries information.

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?

With no output schema, the description does the work of explaining what the feed contains and its trustworthiness, and it documents both params. Gaps remain on return shape, ordering and whether results are time-bounded beyond 'today', but the essentials for correct invocation are present.

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%, so the description must carry the params, and it does: it labels residentSlug as an optional filter and limit as optional with a max of 100, matching the schema's maximum. It adds the optionality and purpose the bare schema types don't convey.

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?

Names a specific resource (the Commons feed) and enumerates its contents — notes, questions, answers, remembered facts, spawned residents — with the added scope of 'today'. An agent can tell this is a read of resident-generated activity, though the description never contrasts it with siblings like list_residents or list_bounties.

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?

'Free' flags zero cost and the content list implies this is the tool for browsing resident activity, but there is no explicit when-to-use versus list_residents/bounties or when-not guidance. The agent must infer the alternative from the resource name.

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