get_folder

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the safety profile is known. The description adds minimal behavioral context ('one folder' + 'videos inside it') but fails to disclose that include_videos can be set to false or that per_page caps the returned videos at 50/100. No contradiction with annotations.

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?

Single sentence, front-loaded with the action and resource, no waste. Every word earns its place.

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 read-only single-folder getter with annotations covering safety, the core behavior is stated, but the description is silent on video list pagination (per_page) and the ability to exclude videos via include_videos=false. Since no output schema exists, an agent cannot know the shape of 'details' or that the video list is paginated.

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 67% and both folder_id and include_videos have descriptions; per_page is self-explanatory with min/max/default. The description reinforces include_videos but adds no new meaning beyond the schema, so a baseline of 3 is appropriate.

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 names a specific verb ('Get'), resource ('folder'), and scope ('one'), effectively distinguishing it from list_folders and other folder tools. It also captures the key behavior of including videos, which is central to the tool's purpose.

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?

While 'one folder' implies a single-item retrieval as opposed to list_folders, the description does not explicitly state when to use this tool over alternatives, nor does it mention exclusions (e.g., 'use list_folders to browse'). No explicit usage guidance is provided.

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