vibemk_get_custom_graph

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

No annotations exist, so the description carries full responsibility. It only says 'retrieve', implying read-only but not explicitly stating it, nor disclosing return format, side effects, or limitations. The minimal wording fails to provide behavioral context.

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 extremely short and front-loaded with the action. However, it includes slight redundancy ('Get custom graph' vs 'Retrieve predefined custom graph data') and lacks depth, though for a simple tool it is appropriately brief.

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?

The description is insufficient for an agent to understand what a custom graph is, what data it returns, or how it fits into the broader monitoring workflow. With no output schema or annotations, the description should compensate but doesn't.

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 coverage is 100% with descriptions for all three parameters (reduce, time_range, custom_graph_id). The tool description adds no extra meaning about parameter usage or relationships, so it neither helps nor hurts beyond the schema.

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 retrieves a predefined custom graph, using specific verbs ('Get', 'Retrieve') and a specific resource ('custom graph'). It distinguishes from sibling tools by being the only graph-specific tool, though it doesn't explicitly differentiate.

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. It doesn't mention conditions like 'use for displaying pre-configured graphs' or contrast with metric tools such as get_host_metrics.

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