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

With no annotations provided, the description carries the full burden of explaining behavior. It states the return values (aggregate trust score and total ratings) and the action 'Get', which implies a read-only operation. However, it does not disclose edge-case behavior (e.g., invalid DID, non-existent agent) or any rate limits or permissions, which are relevant for a query tool.

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 compact and well-structured: a one-line purpose, a one-line return summary, and a clear Args section. Every sentence adds value, and the key action is front-loaded. There is no fluff or redundant information, making it easy for an agent to parse quickly.

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, single-parameter query tool with an output schema, the description covers the essential elements: what it does, what it returns, and how to provide the DID. It omits any mention of error conditions or registration prerequisites, but these are not critical given the tool's simplicity. The presence of an output schema reduces the need to fully enumerate return fields in prose.

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?

Since schema description coverage is 0%, the description must compensate for the single parameter. It does this well by explaining that 'did' is a Decentralised identifier and providing a concrete example format ('did:moltrust:a1b2c3d4e5f60718'). This adds meaning beyond the schema's bare type string, giving the agent enough context to construct a valid value.

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 states the verb and resource: 'Get the reputation score for an AI agent.' It also specifies the return values, which helps differentiate from rate/verify tools. However, it does not explicitly distinguish itself from the sibling mt_get_trust_score, leaving some ambiguity about which tool to pick when a trust score is needed.

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 provides no guidance on when to use this tool versus alternatives such as mt_get_trust_score, moltrust_verify, or moltrust_rate. It only describes what the tool does, without any context about prerequisites, exclusions, or preferred scenarios. This leaves the agent to infer usage from the name alone.

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