memory_trend

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

With no annotations provided, the description carries the disclosure burden. It does reveal a key behavioral outcome: the analysis returns a trend category and slope. It does not explicitly state that the operation is read-only, what data source or time window is used, or any error conditions, leaving some behavioral gaps.

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 a single compact sentence with no filler or repetition. It front-loads the core action and immediately gives the concrete output categories, which is appropriately concise for a tool of this simplicity.

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?

There is no output schema and no annotations, so the description is the only source of operational detail. It mentions the result shape but does not explain the required parameters adequately, does not describe the time interval or data source, and gives no guidance on how this relates to sibling tools. This is insufficient for confident invocation in all cases.

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 adds only minimal meaning: 'metric' maps to '某指标' and the trend is over time. The 'entity' parameter is entirely unexplained, including what kind of entity is expected or how it relates to the metric, so the description does not sufficiently compensate for the bare schema.

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 states a specific verb ('analyze') and resource ('time trend of a metric'), and it names the output categories (rising/falling/flat + slope), making the tool's function clear. It implicitly distinguishes from siblings like memory_anomaly and memory_causal, though it does not explicitly name any alternative.

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 implies this tool is for time-trend analysis of a metric, which gives the agent enough context for a straightforward read-style task. However, it does not state when to prefer it over memory_anomaly, memory_causal, or memory_summary, nor does it mention any exclusion conditions.

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