get_folder_detail

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

The description claims to return a Folder object or ToolError, but it introduces a parameter (folder_properties) not in the schema, suggesting an update behavior that is misleading. No annotations exist, so the description carries full burden, but it lacks true behavioral disclosure.

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 not concise; it includes a leading 'Description:' and rambles about an unrelated update parameter. It could be much shorter and clearer.

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 get-by-ID tool with one parameter and an output schema (not shown but implied), the description covers the basic return value and error. However, the incorrect parameter mention and lack of details on what properties are returned make it less 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?

The input schema has zero description coverage, and the description adds some context for identifier (GUID), but it also mentions an extra parameter (folder_properties) that is not in the schema, causing confusion and reducing reliability.

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 that it gets folder information by ID, which aligns with the name 'get_folder_detail' and distinguishes it from sibling tools like create_folder or update_folder. However, it also mentions 'folder_properties' for updating, causing slight confusion.

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 explicit guidance on when to use this tool versus alternatives like get_folder_documents or update_folder. The description does not provide context for when to fetch folder details or when not to.

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