list_graph_catalog_operations

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

The description mentions 'read-only' and the grouping behavior, which adds some context about the operation's non-destructive nature. But it doesn't disclose authentication requirements, rate limits, or any caveats; with no annotations, the description carries the burden but offers only limited behavioral detail.

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?

A single clear sentence that starts with the verb and conveys purpose and grouping without 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 zero-parameter list operation with an output schema, the description is sufficient: it states the scope (all operations), source (read-only Graph API catalog), and grouping. No return-value explanation is needed due to the output schema.

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?

There are no parameters in the schema, so the description needs no parameter information. Baseline 4 applies since the schema is empty and the description fully clarifies what the operation does.

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 uses a specific verb ('List') and identifies the resource ('operations from the read-only Graph API catalog') and output organization ('grouped by tool/domain'), clearly distinguishing it from siblings like describe_graph_catalog_operation (singular) and discover_graph_operations.

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 specifies it lists all operations and provides grouping context, making clear when to enumerate the catalog. However, it does not explicitly mention alternatives or when not to use it, such as pointing to describe_graph_catalog_operation for details of a single operation.

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