list_ems_systems

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 states this is a listing operation and describes the return format (IDs, names, descriptions), which is helpful. However, it doesn't address potential limitations like pagination, rate limits, authentication requirements, or error conditions that would be important for an agent to know.

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 perfectly concise with two sentences that each serve distinct purposes: the first states the tool's function and strategic importance, the second describes the return format. There's zero wasted text, and information is front-loaded appropriately.

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 the tool's simplicity (zero parameters, has output schema), the description provides adequate context about what the tool does and why to use it. The output schema will handle return value documentation, so the description doesn't need to detail response structure. However, for a tool positioned as an entry point to the system, additional guidance about prerequisites or limitations would be beneficial.

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?

The tool has zero parameters with 100% schema description coverage, so the schema already fully documents the lack of inputs. The description appropriately doesn't discuss parameters, focusing instead on the tool's purpose and output. This earns a baseline 4 for zero-parameter tools that don't waste space on parameter discussion.

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 tool's purpose with a specific verb ('List') and resource ('EMS systems'), making it immediately understandable. It distinguishes itself from siblings by focusing on EMS systems specifically, though it doesn't explicitly contrast with similar tools like 'list_databases' or 'get_assets'.

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 clear context for when to use this tool ('Start here to get system IDs for all other tools'), indicating it's an entry point for subsequent operations. However, it doesn't specify when not to use it or name explicit alternatives among the sibling tools.

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