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

No annotations are provided, so the description carries the full burden. It discloses the returned score types and their range/status format, but does not state that this is a read-only operation, whether it requires specific permissions, or whether scores are live versus stale.

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 that packs the core purpose, score categories, scale, and return shape without any filler. Every clause 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?

For a simple getter with one well-documented parameter and no output schema, the description gives a reasonable overview of the return values (categories, 0-100, status). However, it omits response structure details, freshness guarantees, and error context, leaving gaps that a fuller description could fill when no output schema exists.

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 single targetId parameter is fully documented in the schema with a 100% coverage rate. The description adds no meaning beyond the schema for this parameter, so the baseline score of 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) and resource (composite scores) and enumerates the five score categories plus the 0-100 scale and status rating. It does not explicitly differentiate from siblings like get_target or target_stats, which also return target-level data, 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?

Provides no when-to-use guidance, no alternatives (e.g., recompute_scores, target_stats, get_target), and no prerequisites such as whether the target must exist or whether scores are cached. The purpose implies basic usage but offers no explicit routing.

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