list_globals

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It mentions pagination, which is a key behavioral trait, but doesn't cover other aspects like rate limits, permissions needed, or what happens if parameters are invalid. It adequately describes the core operation but lacks depth for a tool with no annotation support.

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 a single, efficient sentence that front-loads the key information ('List all globals in the database') and adds necessary context ('paginated') without any wasted words. It's appropriately sized for the tool's complexity.

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 annotations and no output schema, the description is minimal but covers the basic operation. It mentions pagination, which is crucial for a listing tool, but doesn't explain return format, error handling, or how it fits with siblings like 'list_globals_filter'. For a tool with 2 parameters and no structured support, it's adequate but has clear gaps.

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 100%, so the input schema fully documents the 'count' and 'offset' parameters. The description adds no additional parameter semantics beyond what's in the schema, such as default values or usage tips. Baseline 3 is appropriate when the schema handles all parameter documentation.

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 verb ('List') and resource ('all globals in the database'), making the purpose specific and understandable. However, it doesn't explicitly differentiate from sibling tools like 'list_globals_filter' or 'get_global_variable_value_by_name', which would require more nuance about filtering vs. 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?

The description provides no guidance on when to use this tool versus alternatives such as 'list_globals_filter' or other global-related tools. It mentions pagination but doesn't explain why or when paginated listing is preferred over filtered or specific value retrieval.

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