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

No annotations are provided, so the description must carry the behavioral burden. It states 'Get' (implying a read operation) but discloses nothing about authentication, rate limits, error handling, or behavior for invalid agent IDs. The minimal wording does not add meaningful transparency beyond the operation itself.

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 a single sentence of 11 words, front-loaded with the verb 'Get.' It is concise, clear, and free of any unnecessary wording, making it easy 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 tool with one parameter and no output schema, the description conveys the essential purpose and expected result (trust score and transaction history). However, it leaves the exact format or details of 'transaction history' unspecified, which prevents a perfect score given the lack of an output schema.

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 agent_id as 'SwarmSync agent ID' with 100% coverage. The description adds no extra parameter semantics beyond what the schema already provides, so it meets the baseline but does not enhance it.

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 uses a clear verb ('Get') and identifies the resource ('trust score and transaction history') with scope ('any agent on SwarmSync'). It clearly distinguishes from sibling tools like swarmsync_check_escrow and swarmsync_hire_agent by focusing on reputation data.

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 a clear context: use this tool when you need an agent's trust score and transaction history. It doesn't explicitly name alternatives or exclusions, but the purpose is distinct enough from siblings (e.g., discover_agents, check_escrow) that an AI agent would know when to select it.

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