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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, covering the safety profile. The description adds that permissions are included in the response, which is useful, but it does not disclose other behavioral aspects like error handling, response structure, or required authentication. Since annotations cover the main safety attributes, a mid-range score is appropriate.

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, information-dense sentence: 'Get a folder's details including permissions.' Every word contributes to the meaning, with no filler or repetition. It is front-loaded and appropriately sized for the simplicity of the tool.

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 read-only tool with strong annotations, the description is minimally sufficient. It states the core purpose and highlights permissions, but does not describe the full return value (given no output schema) or any edge-case behavior. It could benefit from a bit more detail about what 'details' includes, but overall it is adequate.

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 schema has 0% description coverage, and the description does not explain item_id. While the parameter's purpose is somewhat inferable from the tool name and schema (integer, minimum 1), the description fails to explicitly state that item_id is the folder ID or to give any additional semantic meaning. With no description coverage, the tool should compensate; it does not.

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 uses the specific verb 'get' and clearly identifies the resource ('a folder's details'), and the phrase 'including permissions' clarifies what kind of details are returned. This distinguishes it from sibling tools like create_folder, delete_folder, and get_printer/get_print_job, which target different actions or resources.

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 usage is implied by the name and description: when you need details of a specific folder. However, it does not explicitly mention when not to use it or point to alternatives (e.g., listing files or folders), nor does it provide context about prerequisites like needing an item_id. Thus, it provides adequate but not explicit guidance.

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