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

No annotations are supplied, so the description carries the full behavioral burden. It implies a read operation but never states read-only safety, whether results are cached or live, rate limits, or what happens if an unknown provider is requested. For a metrics tool with zero annotation coverage, this is thin.

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?

A single front-loaded sentence with the action and resource first and the optional modifier last. No waste, though the 'optionally with historical trend' clause is somewhat redundant with the schema's trend flag.

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?

With no output schema, the description should describe what 'reputation metrics' actually contains and how the trend is returned. It specifies neither the metric contents nor the relationship between days and trend, leaving the agent unable to anticipate the response for a multi-parameter analytics 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 coverage is 100%, so provider, trend, and days are all documented in the schema. The description reinforces provider scoping and the optional trend, but adds no meaning beyond the schema (e.g., no default trend duration or interaction between days and trend). Baseline 3 is appropriate.

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?

States a specific verb (get), resource (reputation metrics), and scope (a specific oracle provider), with the optional trend qualifier. It is reasonably distinguishable from get_reputation_rankings, though it never explicitly contrasts the two.

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 explicit guidance on when to use this versus alternatives like get_reputation_rankings or get_oracle_health. The phrase 'optionally with historical trend' hints at when to enable trend, but no prerequisites, exclusions, or sibling routing are given.

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