update_all_projectsScans all registered project folders for activity and refreshes their CLAUDE.md files, keeping project context current on demand or via dashboard updates.
Scan all registered project folders for activity. Refreshes CLAUDE.md for each.
Called by the dashboard Update button or on demand.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
| Name | Required | Description | Default |
|---|---|---|---|
| result | Yes |
Changes observed during successful MCP inspections.
v0.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations provided, so description must fully disclose behavior. It mentions scanning and refreshing but does not clarify if 'refreshing' overwrites data, requires permissions, or has side effects. Critical safety details are missing.
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 short sentences, front-loaded with action, no filler. Every sentence 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?
Given no parameters and an existing output schema, description is adequate but lacks mention of performance impact or error scenarios for a bulk operation. Could be more complete.
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?
No parameters exist, so baseline is 4. Description adds meaning by specifying 'all registered project folders', which is beyond the empty schema. No further param info needed.
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?
Clearly states it scans all registered project folders for activity and refreshes CLAUDE.md for each. Verb+resource is specific and distinguishes it from sibling tools like scan_project_folder that operate on single folders.
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?
Provides context (called by dashboard Update button or on demand) but does not specify when not to use it or suggest alternatives like scanning a single folder. Implied usage is clear but lacks exclusions.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.