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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world behavior. The description adds useful scope and approval context: it clarifies that this is organization-level reporting data rather than platform analytics, and that business workflow approvals always apply even though MCP approval requirements are configurable. This goes beyond the annotations without contradicting them.

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 short and front-loads the usage context, followed by scope and approval notes. The phrasing 'working with RetailHardHat reports records' is slightly awkward, but there is no significant filler or repetition.

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 zero-parameter read tool with an output schema and rich annotations, the description covers scope and approval behavior. It is still incomplete on the core question of which metrics are returned and how this tool relates to the many other report-related tools, leaving the agent to infer its role.

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 tool takes zero parameters, so the baseline is 4. The description does not need to explain parameter syntax, and the empty schema is consistent with that.

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 says this reads organization reporting data and excludes platform-level analytics, which gives a basic verb and resource. However, it never specifies what 'metrics' means or how this differs from nearby siblings such as get_report_registry, get_saved_report, run_report, or export_report. The first sentence's 'working with RetailHardHat reports records' is broad and only loosely tied to the tool name.

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?

It gives a very broad usage condition ('when working with RetailHardHat reports records in the connected organization') but no when-not guidance and no routing to alternatives. With many report-related siblings, an agent receives no signal for choosing get_report_metrics over run_report, get_report_registry, or get_saved_report.

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