get_growth_metrics

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

No annotations are provided, so the description must fully disclose behavioral traits. 'Get growth metrics over time' only states the action and resource, but does not mention read-only nature explicitly, authorization requirements, rate limits, or any nuances of the returned data beyond the output schema. This leaves the agent without important safety or context details, though 'get' implies a read.

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 just six words, 'Get growth metrics over time,' which is extremely concise and front-loaded with the intended action. There is no redundant information, making it an efficient single-sentence summary 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?

The tool is relatively simple with two enum-based parameters and an output schema, so the description does not need to explain return values. However, it lacks usage context, such as how this differs from sibling metrics tools or what kind of time-series data is returned. The description is adequate for basic invocation but incomplete for a fully informed agent.

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 input schema fully documents both parameters (metric and period) with enums and descriptions, resulting in 100% schema coverage. The description adds no additional parameter semantics; it only loosely references 'over time' which maps to the period parameter. Baseline score of 3 is appropriate because the schema carries the parameter meaning.

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 'Get growth metrics over time' clearly identifies a read operation for growth metrics with a temporal qualifier. It is specific enough to convey the core function, but does not explicitly differentiate from sibling tools like get_connector_stats or get_crm_stats, which may also retrieve metrics.

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 instead of alternatives, nor any exclusions or prerequisites. Sibling tools such as get_connector_stats and get_crm_stats overlap in purpose, and without clarity on distinguishing use cases, an agent may choose incorrectly.

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