get_favorites

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

With no annotations, the description carries full burden for behavioral disclosure. It only states the basic operation, omitting details about permissions, side effects, or pagination. This is insufficient for an agent to understand all implications.

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 very concise at two sentences, front-loaded with the endpoint. However, it includes an endpoint path which is redundant with the tool name and could be omitted for clarity.

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?

Despite the tool being simple (1 param, no output schema), the description lacks essential context about what 'favorites' are, whether recipes are partial or full objects, and how results are ordered. It is not complete enough for an agent to use confidently.

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?

The input schema has zero description coverage for the sole parameter 'id' (format uuid4). The tool description does not clarify that 'id' refers to the user ID, leaving ambiguity. Parameter semantics are not enhanced 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 states 'Get user's favorited recipes' which clearly identifies the action and resource. It distinguishes from siblings like add_favorite and remove_favorite, but does not differentiate from get_logged_in_user_favorites, which also retrieves favorites but for the current user.

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 (e.g., get_logged_in_user_favorites). There is no mention of prerequisites or context for usage.

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