Get external storage

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

The annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is clear. The description adds minimal behavioral context beyond the resource being fetched, such as 'details' but does not disclose potential errors, permissions, or return format. This is adequate but not rich, given the annotation coverage.

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 a single sentence of nine words, with no filler or redundancy. It directly states the action and target, earning a perfect score for conciseness.

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-ID retrieval tool with a readOnlyHint and no output schema, the description is nearly sufficient. However, it could be improved by referencing the sibling list_external_storages to help discover IDs or clarify what 'details' include. The low complexity makes it workable, but a bit more context would make it complete.

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 description coverage is 100%—the only parameter 'external_storage_id' is documented with its type and description. The tool description adds little beyond echoing the parameter, saying 'one external storage connection,' which does not provide additional syntax or format details. The baseline of 3 is appropriate.

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 clearly states the tool's function: 'Get details of one external storage connection.' The verb 'Get details' and the specific resource 'external storage connection' make the purpose unambiguous. It also distinguishes itself from the sibling 'list_external_storages' by explicitly focusing on a single connection.

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 phrase 'one external storage connection' implies it should be used for a specific external storage ID, but it does not explicitly mention when to use this tool versus alternatives like list_external_storages. No when-not-to-use or alternatives are provided, so the usage context is only implied.

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