Get notifications

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

Discloses that filtering by kind happens after fetching due to a popover behavior, adding value beyond annotations. Annotations already declare readOnly, openWorld, and idempotent hints, so no contradiction.

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 efficient sentences plus a parenthetical note. Front-loads core purpose and key differentiator. No redundant or extra 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?

With full annotations, input schema, and output schema present, the description covers essential behavioral and usage aspects. Could mention pagination or limit behavior briefly, but not necessary given schema.

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?

Description adds semantic context for the 'kind' parameter, explaining why filtering is post-fetch. Schema coverage is 100%, so baseline is 3; the extra explanation justifies a 4.

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?

Clearly states 'Read your Threads Activity feed' with specific examples (follows, replies, mentions, suggestions). Distinguishes from siblings by stating 'every other read tool looks outward', making purpose unambiguous.

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?

Provides context for when to use (find out what happened on your account) and contrasts with other read tools. Mentions optional filtering by kind. Lacks explicit when-not-to-use but is sufficiently clear given sibling context.

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