get_given_recommendations

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

No annotations are provided, so the description must carry the burden. It discloses the pagination requirement and that total count is in the response, but omits potential issues like invalid start values, rate limits, or empty responses.

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?

Single sentence, direct and informative. No wasted words, but could be slightly reorganized to front-load the purpose. Still, efficient for the content.

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?

Missing output schema and no description of the response structure beyond total count. For a scraping tool, an agent needs to know how to extract data from the response. Also, no comparison to similar siblings like 'get_received_recommendations'.

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% but only provides example values. The description adds meaning by explaining that 'start' is used for pagination with increments of 100, which is essential for usage. 'username' is self-explanatory.

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 action ('scrape all recommendations') and resource ('from a profile'). The tool name includes 'given', distinguishing it from the sibling 'get_received_recommendations', so the purpose is 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 explicit pagination instructions: increment start by 100 until total count, which is found in the response. This tells the agent exactly how to iterate through all recommendations.

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