list_favorites

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

No annotations are provided, so the description carries the full disclosure burden and fails it: nothing is said about authentication requirements, result ordering, whether results are the caller's own favourites or another user's, or that the list is paginated. Only the trivial read-only nature is implied by 'List'.

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?

It is a single short sentence with zero waste, so it is appropriately sized, but the brevity comes at the cost of nearly all useful information. Structure is front-loaded yet the content is too thin to earn the space.

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 no annotations, no output schema, and zero parameter documentation, the description would need to explain auth context, pagination, and return shape. It supplies none of these, leaving an agent under-equipped for a tool whose output it cannot otherwise preview.

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?

Two parameters (page, per_page) exist with 0% schema description coverage and no mention in the description, so nothing explains pagination units, defaults, or maximum page size. The only partial mitigation is that these are conventional pagination names an agent can reasonably guess.

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 phrase 'Listings you have favourited' identifies the resource (favourited listings), so an agent can guess this is a read/list operation. But it is a noun phrase that essentially restates the tool name 'list_favorites' and never states a verb, ordering, or scope, so it does little more than the name already does.

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 related siblings such as list_saved_searches or my_items, and no statement of prerequisites (e.g. must be authenticated as the favouriting user). The agent must infer everything about selection from the name alone.

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