list_references

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

With no annotations, the description carries the full disclosure burden, and it says nothing about ordering, pagination, permissions, or whether the list is static. It does hint at the data carried per item (source, licence, scale, matching build), which is mild return-value context, but behavioral traits are essentially undisclosed.

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 no filler, which is good. However, the phrasing is grammatically tangled ('The real-gun photos compare_to_reference measures against'), forcing the agent to re-parse it, and the payload (item fields) is buried rather than front-loaded.

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?

There are no annotations and no output schema, so the description is the only source of behavioral and return information. It gestures at item contents but omits the core action, ordering, and relationship details needed to call a zero-argument list tool 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 tool takes zero parameters, so the baseline is 4 and there is no parameter semantics to add. Schema coverage is reported at 100% for an empty object, so nothing is left undocumented.

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 sentence describes what a reference *is* (source, licence, scale, matching build) rather than stating that this tool lists them. It never uses a verb like 'list' or 'get', so an agent must infer the action from the tool name alone. The resource is identifiable but the operation is not articulated.

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?

The only contextual hook is the mention of compare_to_reference, implying these references are the input that sibling consumes, but there is no explicit when-to-use, when-not-to-use, or alternative-selection guidance. Any usage inference is left to the agent.

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