discover_graph_operations

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

With no annotations, the description carries the full burden. It mentions read-only behavior, but does not disclose authentication needs, scope limitations, or any nuances about the grouping or filtering behavior. Minimal behavioral context is added.

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, front-loaded sentence with no wasted words. It immediately conveys the action, scope, and organization of results.

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?

Despite the simple tool shape, the lack of annotations, undocumented parameter, and no usage guidance leaves gaps. The output schema exists, but the description still under-specifies behavior and alternatives, making it only minimally complete.

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 single 'category' parameter has zero schema description. The description mentions grouping by tool/domain but does not explain how the category parameter is used, its possible values, or its effect on the output. Only marginal meaning is added.

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 lists all supported read-only Graph operations grouped by tool/domain, using a specific verb and resource. It distinguishes from management-focused siblings, though it does not explicitly differentiate from the similar list_graph_catalog_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?

No guidance is provided on when to use this tool versus alternatives like list_graph_catalog_operations or describe_graph_catalog_operation. The intended use as a discovery tool is implied but not explicitly stated.

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