get_agent_relationships

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

No annotations provided; description only states listing, implying read-only. Does not disclose authentication, rate limits, or any side effects. Minimal transparency beyond the verb.

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?

Very concise: 2-line summary then structured Args section. No fluff, every word 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?

Covers input parameters well and purpose is clear. Output schema exists so return values are defined. Could mention behavior if agent_id is invalid, but not essential for a simple list 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?

Schema coverage is 0% (no descriptions in schema). Description adds clear semantics: agent_id is 'Canonical chainId:agentId identifier' and direction is 'One of incoming, outgoing, or both (default)'. Adds meaning beyond bare types.

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?

Starts with 'List relationships for a specific agent' – clear verb and resource. Distinguishes from siblings like get_agent (gets a single agent) and get_recent_relationships (no specific agent filter).

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?

Implies use when you need relationships filtered by agent_id, but no explicit when-not-to-use or alternative suggestions among siblings.

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