recommend_content

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

No annotations provided; description mentions analyzing timeline, engagement, and network, implying read-only behavior. However, it lacks details on authentication, rate limits, or side effects, leaving some ambiguity.

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 are concise, but the brevity sacrifices critical details about parameters and usage context. The structure is front-loaded but incomplete.

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 5 unannotated parameters and no output schema, the description is insufficient for an agent to correctly invoke the tool. It lacks parameter explanations and usage constraints.

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 description coverage is 0%, yet the description does not explain any of the 5 parameters (maxResults, minLikes, maxAge, topics, excludeReposts). The agent cannot infer parameter meanings from the description alone.

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 tool recommends posts using user interests and engagement history. However, it could better differentiate from siblings like search_posts or get_custom_feed, which also return content.

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?

No explicit guidance on when to use this tool over alternatives. With many sibling tools for content discovery, the description should clarify scenarios for recommendations versus search or timeline retrieval.

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