stores_favorites

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds the useful scope qualifier that only pickup restaurants are returned, but says nothing about ordering, pagination, or what a 'saved favorite' entry contains (no output schema exists to cover that).

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?

One short sentence, front-loaded with the verb and scope, with zero filler. Nothing extraneous to trim.

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 list tool with no output schema and an undocumented required account parameter, the definition leaves too much open: account identifier format, result shape (list of stores? IDs?), and any limits are all unstated.

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 0% and the single required parameter 'account' is undocumented in both schema and description. The phrase 'this account's' gestures at the parameter but never says whether it is an ID, email, or handle — the description fails to compensate for the coverage gap.

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 names a specific verb ('Read') and resource ('saved pickup restaurants'), so the agent knows this returns the account's favorites list rather than store details. It stops short of differentiating from siblings like store_get or accounts_list, which could matter given the surrounding catalog.

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 statement of when to prefer this over alternatives — e.g. store_get for a single location or accounts_list for picking the account. The 'pickup' qualifier hints at a filter but no condition or exclusion is articulated.

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