Bill Graph Data

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

The annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety and side-effect profile is already known. The description adds no additional behavioral context such as data granularity, graph type implications, timezone handling, or output characteristics beyond what the schema and annotations already provide.

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 compact sentence with no fluff, though 'from LibreNMS' is somewhat redundant given the tool context. It is front-loaded and efficient, but slightly thin in substance.

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 simple read-only two-parameter tool with an output schema, the mechanics of invocation are covered by the schema and annotations. However, the description alone does not fully disambiguate this tool from the many related bill graph/history siblings, so completeness is only minimally adequate.

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 two parameters are already adequately described in the input schema. The tool description itself contributes no extra parameter-level meaning, placing it at the baseline for high coverage.

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 ('Get') and a clear resource ('bill graph data'), so an agent can tell it is a read operation for billing graph information. It does not explicitly differentiate itself from sibling tools like bill_graph or bill_history_graph_data, so it misses the top score.

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. Given many sibling graph tools such as bill_graph, bill_history_graph, and bill_history_graph_data, an agent has no stated selection criteria, exclusions, or hints about which one fits a given request.

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