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

With no annotations provided, the description carries the full behavioral burden. It does disclose what output entries contain (relationship, shared wording, canonical URLs), but it omits side-effect/safety information and edge behavior like pagination, error handling, or how defaults such as translation and limit apply.

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 concise sentence that front-loads the core purpose. It avoids fluff and is easy to scan, though the poetic phrase 'the lateral axis' adds slight ambiguity without much practical value.

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?

The tool has no annotations, no output schema, and a schema with no parameter descriptions, yet the description does not fill those gaps. It gives a sense of the data shape but leaves out usage context, parameter behavior, and expected return structure, so an agent would struggle to invoke it correctly.

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 input schema contains no descriptions for any of the four parameters, and the description does not explain reference, limit, translation, or relationship_type. An agent cannot determine valid values, allowed relationship types, or how translation affects results, making parameter usage effectively undocumented.

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 identifies the resource as 'the connections recorded for a verse' and implies an action of retrieving them. It states what each connection carries, giving a clear picture of the tool's purpose, though it does not explicitly distinguish itself from siblings like get_connection or search_verses.

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 given about when to use this tool versus alternatives such as get_connection, find_path, or search_verses. The description only implies that this tool is for retrieving verse connections, leaving the agent to infer the appropriate context.

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