List User Data

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

No annotations provided; description adds return format but does not disclose safety (e.g., read-only, permissions, side effects). Adequate for a simple enumeration but missing behavioral details.

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 concise sentences front-loading the action and return format, with zero wasted words.

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 enumeration tool with one parameter and no output schema, the description covers purpose, return structure, and downstream usage. Lacks error handling or edge cases but sufficient for selecting and invoking the tool.

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 covers the handle parameter minimally ('Target to inspect.'). The tool description adds value by explaining the return structure and how desc_id is used, compensating for the schema's brevity.

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 the action ('Enumerate') and resource ('User Data slots on a target'), and specifies the return fields {desc_id, name, dtype, value}, distinguishing it from sibling tools.

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 clear context: enumerate user data slots and feed desc_id into downstream tools. Lacks explicit when-not-to-use or alternatives, but the specific use case is well-defined.

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