Unpin Feed

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

No annotations exist, so the description conveys key behavior: the feed remains subscribed but headline display stops. It lacks details on error handling or idempotency, but is sufficient for a simple toggle.

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 concise sentences directly convey purpose and effect without extraneous 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?

For a simple toggle with no output schema, the description covers the essential behavioral change. It could mention idempotency or error cases, but overall is adequate.

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 100%, so baseline applies. The description adds no extra information about the feed_id parameter beyond what the schema provides, but that is acceptable.

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 specifies the action (unpin), the resource (feed), and the consequence (removes from morning briefing), effectively distinguishing it from related operations like unsubscribe.

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 explicitly states when to use the tool: to stop seeing headlines in session start while keeping the subscription. It implicitly contrasts with unsubscribe, providing clear contextual guidance.

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