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

No annotations exist, so the description carries the full burden. It discloses important behavioral traits: one point per scored build, composite plus agent readiness, and a summary of movement. Crucially, it clarifies that these are recorded snapshots, not implied or interpolated points, which is a meaningful non-obvious behavior that helps set expectations.

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 two sentences and contains no filler; it front-loads the core idea of a 'real score time series' and then adds the summary fields. The long dash-heavy first sentence is somewhat dense, but every clause contributes information about what the tool returns.

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 there is no output schema and no annotations, the description covers the return payload in useful detail: per-build points, composite and agent readiness, and summary fields. The main gap is the undocumented slug parameter and the exact response shape, but the prose is sufficient for an agent to invoke the tool with a provider identifier and understand what it will receive.

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 schema describes only the context parameter; the required slug has no description, and schema coverage is only 50%. The tool description does not compensate: it never explains what slug is, how to format it, or how it maps to a provider. With such low coverage, the description needed to handle this and did not.

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 clearly identifies the resource and output: a provider's score time series with composite and agent readiness per scored build, plus a movement summary. It makes the tool's purpose unambiguous. However, it does not explicitly name or distinguish sibling alternatives like get_provider_rating or whats_changed, so it falls short of a 5.

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 usage: an agent would use this when it needs a provider's recorded score history over time. But there is no explicit guidance about when to choose this over sibling tools such as get_provider_rating, find_ratings, or whats_changed, and no when-not-to-use conditions are provided.

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