get_folder_detail

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

The description claims to get folder info but introduces update-like language, misrepresenting behavior. It also mentions a non-existent parameter 'folder_properties', further confusing the agent. No annotations are provided, so the description carries the full burden, which it fails.

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 includes three blocks: a purpose statement, a parameter list with an incorrect parameter, and a return statement. The inclusion of irrelevant and incorrect content makes it wasteful and confusing, not concise.

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 (single parameter, output schema exists), the description should clearly state that it retrieves folder details. Instead, it conflates getting and updating, omits necessary behavioral details, and contradicts the schema. The output schema may cover return format, but the behavioral confusion persists.

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 only one parameter 'identifier', but the description lists two parameters, including 'folder_properties' which does not exist in the schema. With 0% schema description coverage, the description should clarify parameters but instead introduces false information.

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 first sentence clearly states 'Get an existing folder...given a folder id', aligning with the tool name. However, the description then contradicts itself by mentioning 'Properties to update for the folder', which implies a mutation operation. This inconsistency muddles the purpose and misleads the agent.

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 get_folder_documents or update_folder. There is no mention of prerequisites, exclusions, or context that would help an agent decide between sibling tools.

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