get_profile_reels

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

Without annotations, the description carries the full burden of behavioral disclosure, but it only states what the tool does, not its side effects, authentication needs, or rate limits. The read-only nature is implied but not confirmed, and no details about pagination or result format are given.

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?

The description is a single sentence with no unnecessary words, achieving conciseness. However, it is overly brief, sacrificing completeness for brevity, which could be improved by adding a second sentence on parameter usage.

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 the tool has 3 parameters and an output schema, the description is incomplete. It does not explain the required 'target' parameter, default values, or behavioral aspects like pagination. While the output schema covers return values, the description lacks essential context for effective selection.

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?

With 0% schema description coverage, the description should explain parameter meanings. It only mentions 'days_back' as optional, but does not explain 'target' (e.g., username vs. ID) or 'limit' (e.g., maximum count). The summary adds minimal value beyond the schema.

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 retrieves reels for a profile with an optional days_back filter, distinguishing it from sibling tools like get_hashtag_reels and get_recent_reels. However, it lacks explicit mention that 'target' refers to a profile identifier.

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 guidance is provided on when to use this tool versus alternatives such as get_profile_reels_page for paginated results or get_hashtag_reels for hashtag-specific reels. The description does not indicate any prerequisites or contexts where this tool is preferred.

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