list_global_subscripts

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

Describes the ZORDER-style iteration, recursion behavior, max_nodes limit, and include_values option. No annotations provided, so description carries burden; it sufficiently explains the read-only nature and major behaviors.

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?

Well-structured with bullet points for parameters and clear hierarchical purpose statement. Slightly verbose but every sentence adds value; could be tightened slightly.

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?

Covers parameters well and output schema exists, so return format is not needed. Lacks mention of error conditions or performance considerations, but overall adequate for a listing 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 coverage is 0%, but the description thoroughly explains all 6 parameters, adding meaning (e.g., 'global without ^', 'path into the global', default values, behavior of recursive and max_depth). Greatly compensates for missing schema descriptions.

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 the tool lists subscript keys under a global path using IRIS node iterator. Differentiates from siblings (e.g., check_global, save_global) by focusing on subscripts listing.

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?

No explicit guidance on when to use this tool versus alternatives. Does not mention when not to use or provide context for selecting this over other global-related tools.

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