vrm_get_overall_stats

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

With no annotations, the description carries full burden. It states what the tool returns but does not disclose behavioral traits such as read-only nature, authentication requirements, rate limits, or error handling. For a tool with untagged safety profile, more detail is needed.

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?

Single sentence with front-loaded key information: what the tool does and its scope. No unnecessary words or repetition. Efficient and clear.

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?

Description is adequate for a simple aggregate retrieval tool, but given complex time period logic and no output schema, it lacks guidance on return format or how to use type parameter effectively. Could be more complete for a tool with 5 parameters.

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 baseline 3. The description adds no additional meaning beyond the schema; it does not explain parameter relationships (e.g., type vs start/end). The schema already documents each parameter adequately.

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?

Description clearly states 'Get aggregated energy totals' with specific resources (solar yield, consumption, battery performance) and time scopes (daily, monthly, yearly), effectively distinguishing from sibling tools like vrm_get_stats for non-aggregated data.

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?

Description implies usage for aggregated totals but provides no explicit guidance on when to use this tool versus alternatives like vrm_get_stats or vrm_get_data_attributes. No when-not or exclusion criteria.

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