shortlist_show

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

With no annotations, the description carries the full behavioral burden, and it discloses nothing: not whether the list is per-user or global, whether it is empty by default, or whether it has side effects. The only behavioral hint is the verb "show", which is minimal for a zero-annotation tool.

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 and contains no filler, but the brevity is under-specification rather than tightness: it is front-loaded on nothing and gives the agent no extra anchor. A marginally longer description naming the return content would earn the same score more convincingly.

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?

An output schema exists, so return values need not be explained, but with zero annotations and a one-line description the agent still lacks scope, preconditions, and sibling routing. For a shortlist-read tool sitting next to export/add/remove siblings, that leaves meaningful gaps.

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 tool takes no parameters, which is the stated baseline of 4. The description adds nothing about filtering or scoping options, but there is nothing to add given the empty 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 names the resource and a display action ("Показать шорт-лист" = show the shortlist), so the basic intent is legible. However, it offers no differentiation from siblings such as shortlist_export (which presumably also displays/returns the list) or shortlist_add/remove; the agent must infer the boundary from names alone.

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 when-to-use guidance, no mention of prerequisites (e.g. whether items must first be added), and no stated alternative such as shortlist_export for retrieving data. The agent is left to guess the use case from the tool name.

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