get_folder_details

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

No annotations provided, so the description should disclose behavioral traits. It implies a read operation but does not explicitly state it's read-only or mention any side effects, required permissions, or limitations. The presence of an output schema reduces the need for return value details, but basic behavioral disclosure is missing.

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 extremely concise: a one-line purpose followed by an Args list. No unnecessary words, every sentence adds value. Front-loaded with purpose first.

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 the tool is a simple get with 2 parameters and an output schema exists, the description is minimally adequate. However, it lacks context like the origin of folder_id (e.g., from list_folders) and error handling or conditions. Not fully complete for an agent to use without assumptions.

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 0%. The description lists parameters hostname and folder_id with a note 'hostname: vSphere hostname (e.g., vcenter.domain.local)' but does not explain the format or purpose of folder_id beyond its name. Parameter semantics are minimal and insufficient for an agent to know how to fill them correctly without external knowledge.

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 'Get detailed information about a folder', specifying the verb (Get), resource (folder), and scope (detailed). This distinguishes it from siblings like list_folders which just list folders.

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 description implies using this tool when you need details for a known folder_id, but it does not explicitly state when to use it versus alternatives like list_folders or other get tools. No exclusions or when-not-to-use guidance.

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