List files and directories in your persistent execution workspace (created with use_workspace=true on execute calls). Extremely useful for multi-step coding, data work, and repo-based agents. Free.
| Name | Required | Description | Default |
|---|---|---|---|
| path | No | Relative path inside the workspace (default: root) | . |
| agent_id | Yes | Your agent identifier |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=true, and the description adds context about the workspace being persistent and created with use_workspace=true. It also notes the tool is 'Free', which is a behavioral trait not captured in annotations. No contradictions.
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 two sentences, front-loaded with the core purpose, followed by usage value and cost. Every sentence earns its place with no redundancy or fluff.
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 read-only list tool with good annotations, the description covers purpose, workspace context, usage scenarios, and cost. However, it does not mention return value format or edge cases like hidden files or recursion, which would make it fully 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?
Both parameters are fully documented in the schema (coverage 100%), so the description does not need to add parameter details. It provides no extra meaning beyond the schema, aligning with the baseline for high schema coverage.
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 'List files and directories in your persistent execution workspace', which is a specific verb+resource and distinguishes it from sibling tools like workspace_delete and workspace_status. The context about use_workspace=true further clarifies the tool's scope.
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 gives clear context on when to use it ('multi-step coding, data work, and repo-based agents'), but it does not explicitly mention when not to use it or alternatives. This is strong implied usage guidance, though it lacks explicit exclusions.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Most tools have clearly distinct purposes, but there is potential confusion between 'decision' and 'reason', both offering advisory output. Also, 'review', 'witness', 'prove', and 'verify_proof' overlap in the proofs space, though descriptions differentiate them. Overall, an agent can disambiguate with careful reading.
All tool names use lowercase and underscores (snake_case), which is consistent. However, the verbs vary: some are imperative (e.g., 'browse', 'execute'), while others are nouns (e.g., 'signals', 'ledger'), breaking a strict verb_noun pattern. Overall, the naming is readable and mostly predictable.
With 30 tools, the surface is too large for a well-scoped server. Many functions could be separated (e.g., memory, workspace, feedback, marketplace). This excess makes it harder for an agent to navigate and select the right tool quickly.
The tool set covers core CRUD for memory and workspace, plus feedback, marketplace purchase, bounties, and verification. However, there is no tool to list or search marketplace listings, and workspace creation is only implicit via 'execute'. These gaps hinder fluid workflows.
