lookup_storage

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

With no annotations, the description carries the full burden. It discloses that the tool returns existence and details, which is useful, but it does not mention error behavior, permissions, or side effects. For a read-only lookup, this is minimal but not insufficient.

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 description is very concise: one purpose sentence followed by a single parameter definition. It is well-structured, front-loaded, and every sentence earns its place.

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 simple single-parameter lookup tool, the description covers the core purpose and parameter semantics. The existence of an output schema means return values do not need to be explained further. It could mention when to use, but that is not critical here.

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 input schema has only a bare 'name' string, but the description adds meaning: 'Storage name as configured in duplicacy-web.' This contextualizes the parameter beyond the schema, compensating for 0% schema description coverage.

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: 'Look up a storage by name; returns whether it exists and its details.' This clearly distinguishes it from sibling tools like create_storage and delete_storage.

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 intended usage is implied through the verb 'look up,' but the description does not explicitly state when to use it versus alternatives, nor does it provide exclusions or prerequisites. It is clear enough for a simple lookup operation.

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