get_favorites

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

No annotations are provided, so the description carries the full burden, and it discloses almost nothing: no pagination, no permission requirements, no return shape, no error behavior. The lone 'read-only' token buried in the keyword soup is the only behavioral hint.

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 first two lines are reasonably front-loaded, but the definition is padded with an enormous redundant keyword list ('get favorite, list favorite, search favorite… read-only, mealie') that repeats the same concept a dozen times without adding information.

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?

For a read tool with no annotations and no output schema, the agent lacks any signal about what comes back, whether results are paginated or scoped to permissions, or how to interpret them. The description should do more than restate the endpoint.

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 sole 'id' parameter is undocumented in the schema. The route template [GET /api/users/{id}/favorites] does implicitly tell the agent the id is a user id, which is real added value, but the format (uuid4) and constraints come only from 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 a specific verb and resource: 'Get user's favorited recipes,' reinforced by the route [GET /api/users/{id}/favorites]. It is distinguishable from the sibling get_logged_in_user_favorites because it takes an explicit user id, though the description never makes that distinction explicit.

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?

There is no guidance on when to use this versus get_logged_in_user_favorites, add_favorite/remove_favorite, or get_ratings. The keyword list mentions 'users ratings' and 'read-only' but that is retrieval bait, not usage direction.

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