list_workspace

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

No annotations provided; description carries full burden. It describes the function as inventorying but does not disclose whether it is read-only, requires authentication, or has side effects. The term 'inventory' suggests read-only but is not explicit.

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, no wasted words. Clearly communicates the tool's core function. However, it could be restructured to include parameter context or usage tips without adding length.

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?

Tool is simple with one parameter and has an output schema, so description doesn't need to explain return values. However, it lacks usage guidelines and behavioral transparency. Acceptable for a basic tool but could be more informative.

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 coverage is 0%, so description must compensate. The description mentions 'workspace (geodatabase or folder)' which hints at the 'path' parameter meaning, but does not explain it directly or provide format/constraints. No additional value beyond schema.

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?

Description clearly states the verb 'inventory' and resource 'workspace (geodatabase or folder)', and lists the types of contents (feature classes, rasters, tables, datasets). It distinguishes from siblings like 'describe_data' by focusing on listing contents.

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 implies usage for inventorying workspace contents but provides no explicit guidance on when to use this tool versus alternatives like 'describe_data' or 'inspect_project'. No when-not-to-use or prerequisites mentioned.

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