overview_charts

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

With no annotations, the description carries the full behavioral burden, and it discloses only that the `reports:manage` permission is required. It does not say what data the charts return, whether the result is cached or rate limited, or what an empty result looks like. The permission note is genuinely useful, but it is the only behavioral fact provided.

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?

It is short and front-loaded, but the opening line is a title restatement and the trailing HTTP path and tag metadata add little for an agent. The permission requirement is the only sentence that earns its place.

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 read-only reporting tool with no output schema and no annotations, the description should convey what the charts show and what the response looks like. Neither is present, leaving an agent unable to predict the result or choose this over sibling overview tools.

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% and the single `days` parameter is thoroughly documented, including the 0-365 clamping behavior, so the schema does the heavy lifting. The description adds nothing about `days` or its defaults. Baseline 3 applies.

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 first line, "Get Overview Charts," simply restates the tool name rather than describing what the charts contain or represent. The only added specificity is the HTTP path and tag, which tell an agent little about the resource beyond its name. None of the adjacent overview_* siblings are distinguished.

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 gives no when-to-use or when-not-to-use guidance, and no indication of how this differs from overview_counts, overview_csat, or the other overview siblings. The only context is an access requirement, which is a prerequisite rather than usage guidance.

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