List Users Self Favorites

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

With no annotations provided, the description carries the full burden of behavioral disclosure. The word 'Get' suggests a read-only operation, but the description does not state authentication expectations, whether the result is paginated, whether favorites refer to recipes or another entity, or any other behavioral details. This is minimal disclosure rather than transparent behavioral guidance.

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 short sentence with no filler or redundant phrasing. It front-loads the core purpose and is appropriately compact, though its brevity leaves important context unaddressed.

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?

The description is too sparse for a tool with no annotations: it does not specify what the favorites contain, does not clarify the relationship to list_users_by_id_favorites, and does not explain the optional accept-language parameter. While an output schema exists and may cover the return shape, the description alone is insufficient for an agent to confidently select and invoke this tool in all relevant situations.

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%, and the description does not mention the accept-language parameter at all. The schema only indicates it is a nullable string, leaving its purpose and effect entirely undocumented. The description fails to compensate for the schema's lack of parameter documentation.

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 'Get Logged In User Favorites' uses a clear verb and resource, and the 'Logged In User' qualifier distinguishes this from list_users_by_id_favorites and other user-scoped endpoints. It is specific enough that an agent can infer the operation, though it does not explicitly name a contrasting sibling.

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?

The phrase 'Logged In User' implies this is for the current authenticated user's favorites, which gives some usage context. However, there is no explicit guidance about when to choose this over list_users_by_id_favorites, list_users_self, or list_users_self_ratings, and no exclusions or alternative routing are provided.

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