get_folder_details

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

With no annotations provided, the description carries the burden of behavioral disclosure. 'Get' conveys a read-only, non-mutating operation, which is a useful behavioral signal. It does not mention authorization, scoping, or error behavior, but for a simple getter with an output schema this is a acceptable minimal 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 a single, front-loaded sentence with no filler words. Every word earns its place, and it is appropriately sized for a simple getter 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?

Given that there are only two required parameters with fairly clear names and an output schema exists, the description is minimally viable. It lacks usage guidance and parameter elaboration, but for a straightforward read-only tool, the combination of name, description, schema, and output schema may be enough for an agent to call it correctly.

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 description coverage is 0%, so the description needed to compensate by explaining account_id and folder_id, but it does not. It only refers to 'specific folder details,' giving no additional meaning or relationship between the two parameters. The parameter names are somewhat self-explanatory, but no real semantic guidance is added.

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 the action ('Get') and the resource ('specific folder details'), which indicates a read operation for an individual folder. The word 'specific' helps separate this from get_all_folders, though it does not explicitly name any sibling or clarify 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?

The phrase 'specific folder details' implies this should be used when the agent needs information about one folder rather than the full list from get_all_folders. However, it does not explicitly state when to use this tool over alternatives or give any exclusions or prerequisites.

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