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

Annotations already indicate read-only, idempotent, and non-destructive behavior. The description adds no additional behavioral context, such as return format, pagination, or specific growth metrics included. While the annotations cover safety, the description fails to clarify what 'growth rates' entails, leaving significant ambiguity.

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 extremely short (two words), but this is under-specification rather than conciseness. It lacks structure and substantive content. While it is front-loaded, it does not earn its place as it conveys almost no useful information.

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?

Given the tool has three parameters, no output schema, and zero schema description coverage, the description is grossly inadequate. It does not explain what data is returned, how parameters interact, or any limitations. It is incomplete even for a simple lookup tool.

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 0%, and the description does not explain any of the three parameters (symbol, period, limit). There is no mention of what 'period' values are valid, what 'limit' controls, or that 'symbol' is required. The example in the schema helps, but the description itself provides no parameter semantics.

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 'Growth rates.' is a noun phrase that identifies a resource but lacks a verb indicating an action. It is slightly more specific than a pure tautology but does not clearly state what the tool does, such as retrieving or calculating growth rates. It also does not differentiate itself from sibling tools like 'ratios' or 'key_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?

There is no guidance on when to use this tool versus alternatives. The description provides no context, prerequisites, or exclusions. It is completely silent on use cases, making it impossible for an agent to know if this is the right tool for a given task.

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