get_feed

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

Starts with 'Read-only' indicating no side effects, and describes the return format. Without annotations, this is good but could mention pagination or rate limits.

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 sentences, highly efficient, front-loads the essential info (read-only, purpose), no redundant text.

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?

Covers purpose, parameters with examples, return fields, and alternatives. Lacks mention of authentication, error cases, or pagination, but acceptable for a simple feed retrieval tool.

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?

Adds meaningful examples for 'tab' parameter (for-you, subscribed, category-slug) and hints at limit affecting list size, but does not elaborate on limit's exact role. Schema has 0% coverage, so description helps but not fully detailed.

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 verb 'Pull' and the resource 'reader feed', and distinguishes from siblings list_posts and search_posts by specifying their use cases.

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 explicit when-to-use instructions with tab options and directs to alternatives: 'For a single publication's chronological list use list_posts; for keyword search use search_posts.'

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