create_friend_info_folder

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

No annotations are provided, so the description carries full burden. It discloses that only creation is allowed and no update/delete, which is important behavioral info. It does not mention permissions or side effects, but for a simple folder creation, this is adequate.

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?

Two sentences, no wasted words. First sentence states action and purpose, second sentence adds a crucial constraint. Front-loaded with key info.

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 creation tool with one required parameter and no output schema, the description is fairly complete. It explains purpose, the resource type, and the only limitation. Could be improved by noting that folders are used to organize custom attributes, but it's already implied.

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 100% coverage with one parameter 'name'. The description adds context by explaining what the folder is for (organizing friend info), which gives semantic meaning beyond the schema's 'folder name'. This compensates for the lack of param details.

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 it creates a folder for organizing friend information, explicitly distinguishing it from sibling tools like create_tag_folder by specifying 'friend info'. The verb 'create' and resource 'folder' are specific.

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 notes that only creation is possible and no delete/update APIs exist, which helps the agent set expectations. However, it does not explicitly compare to alternatives like create_tag_folder, though the context implies the distinction.

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