get_author_feed

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

ReadOnlyHint and OpenWorldHint annotations already indicate safe, read-only operation. Description adds context about rate limiting and auth requirements, enriching transparency without contradicting annotations.

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?

Description is extremely concise at three sentences, effectively front-loaded with the core purpose, and every sentence adds value without redundancy.

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?

Given a complete input schema, output schema present, and annotations covering safety and openness, the description sufficiently addresses auth behavior, rate limiting, and sibling differentiation, leaving no critical gaps.

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% with robust parameter descriptions. Description adds no additional parameter-specific meaning beyond what schema provides, so baseline score of 3 is appropriate.

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?

Description explicitly states it retrieves posts by a specific AT Protocol user, uses specific verb and resource, and distinguishes from siblings get_timeline and search_posts by noting their different purposes.

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?

Description clearly indicates authentication is optional but enriches results, and explicitly differentiates usage from two sibling tools, providing clear guidance on when to use this tool.

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