mc_getFileFolder

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

Without annotations, the description implies a read operation with no side effects, which is appropriate for a get tool. However, it does not disclose any potential restrictions, authentication needs, or response behavior beyond the obvious.

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, concise sentence with no unnecessary words. It is front-loaded and efficient.

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's simplicity and lack of output schema, the description is adequate but could be more complete by indicating what 'details' are returned (e.g., name, path, permissions). It does not fully inform the agent of the tool's capabilities.

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 coverage is 100% for the single parameter folderId. The description does not add any additional meaning beyond the schema's type and 'The unique ID for the file folder'.

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 'Get file folder details' clearly states the verb and resource, distinguishing it from sibling tools like mc_listFileFolders and mc_getFile. However, it lacks specificity on what 'details' includes.

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?

No guidance on when to use this tool versus alternatives like mc_listFileFolders for listing folders or mc_getFile for file details. The description does not provide context for selection.

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