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

No annotations are provided, so the description carries the full behavioral burden. It states the output is a composite score with pillar breakdowns and methodology version, which is useful, but doesn't specify refresh cadence, data sources, historical availability, or what 'methodology version' means for interpretation. For a data-read tool with no annotations, this is incomplete.

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 well-structured sentence front-loads the key purpose (weekly composite score) and then details its components. It is efficient and information-dense without redundancy, though slightly long for a zero-parameter getter.

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 no output schema, no annotations, and zero parameters, the description must convey the return value's shape and the tool's operational context. It describes the output as a composite score with pillar numbers and methodology version, but omits cadence details, freshness guarantees, and how to interpret the score—gaps that matter for a monitoring 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?

The tool has zero parameters, so there are no parameter semantics to document. The baseline score is 4 per the rules (0 params = baseline 4), and the description appropriately does not waste space on non-existent parameters.

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 (returns/describes) and resource (the weekly Agent Trust Index, a composite 0-100 score), and details its composition (code-safety, identity, supply-chain pillars). This clearly distinguishes it from data-fetching siblings like get_mcp_ecosystem_stats which covers ecosystem metrics, not a fused trust score.

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 (retrieve the current trust index) but doesn't explicitly state when to use this vs alternatives like get_threshold_watch or get_agent_identity_tracker. No exclusions or prerequisites are mentioned.

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