Skip to main content
Glama
CROW: LLM Wiki

CROW: LLM Wiki

Official

describe_folder

Updates a folder's one-line routing description so new notes follow the revised purpose; already filed notes stay put.

Instructions

Change a folder's one-line description, the line new notes are routed by.

Call it when the user redefines what a folder is for; to rename it, use rename_area; to move notes already filed, move_note. Notes already filed stay where they are: only new notes follow the new line. Returns the folder and its new description.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "folder": "<folder>",
      "description": "<description>"
    },
    "name": "describe_folder"
  }
}

Input Schema

NameRequiredDescriptionDefault
folderYesThe folder, e.g. /finance
descriptionYesOne line: what belongs in it

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.4

TDQS

A4.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=false with destructiveHint=false, and the description corroborates that by disclosing the exact blast radius: 'Notes already filed stay where they are: only new notes follow the new line.' That non-obvious retroactivity constraint is the most valuable sentence here. It stops short of permissions or failure mode detail, but combined with the annotations this is strong coverage.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three short sentences: the action, the routing guidance, and the side-effect constraint. The key distinguishing fact (existing notes do not move) is stated before the return-value sentence, and nothing is redundant with the title or schema.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

A two-parameter mutation tool with an output schema, so return values need no explanation, yet the description still notes it returns the folder and new description. Trigger, alternatives, and effect scope are all present; an agent has everything needed to call it correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3, but the description adds real meaning: it establishes that the description is a functional routing line rather than a cosmetic label, and that changing it is how the user 'redefines what a folder is for'. That reframes the 'description' parameter beyond the schema's 'One line: what belongs in it'.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

Names a specific verb and resource ('Change a folder's one-line description') and immediately states the resource's function ('the line new notes are routed by'). It explicitly distinguishes itself from rename_area and move_note, so an agent can tell the three apart without opening any schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives an explicit trigger ('when the user redefines what a folder is for') and routes the two nearest alternatives: rename_area for renaming, move_note for re-filing existing notes. Nothing about when to pick this over a sibling is left to inference.

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