list_relationships

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

With no annotations, the description should disclose behavioral traits. It does not mention that the tool supports pagination (limit/offset), filtering by direction or relationship type, or that it uses a legacy entity_id pattern. The schema provides these details but the description lacks a high-level behavioral summary.

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 with no unnecessary words. It is efficiently structured and front-loaded with the core purpose.

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 8 parameters with full schema coverage, no annotations, and no output schema, the description is too brief. It should at least summarize the key capabilities: listing relationships with filtering by entity, direction, type, and pagination. The current description leaves the agent to parse the schema completely.

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 100%, so the baseline is 3. The description does not add any parameter insights beyond what the schema already provides. For instance, it does not explain the interaction between entity_id and direction, or that source_entity_id and target_entity_id are alternatives.

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 'List relationships for an entity' clearly states the action and resource. It is specific enough, though it does not differentiate from sibling tools like 'get_relationship_snapshot' or 'create_relationship'. However, the name itself provides some differentiation.

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?

No guidance is provided on when to use this tool versus alternatives. For example, there is no mention that for a single relationship snapshot one should use 'get_relationship_snapshot', or that filtering by type is available. The agent must infer usage from the schema alone.

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