getRelationship

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

With no annotations provided, the description carries the full burden of behavioral disclosure. The verb 'get' implies a read-only operation, but the description does not explain what happens if the ID is not found, what the response contains, or any side effects (e.g., marking something as read). This is minimal transparency.

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 is front-loaded with the verb and resource. Every word earns its place, and there is no redundant or filler content.

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 there is no output schema, the description should explain what the tool returns or at least define what a 'relationship' is in this context. It does neither, leaving the agent to infer the return payload and relationship semantics. For a simple getter, this is an adequate skeleton but lacks necessary context to fully invoke 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 already describes the only parameter ('id' as 'Relationship ID') with 100% coverage. The description adds no additional meaning beyond the schema, so the baseline of 3 applies; it neither enhances nor detracts.

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 'Get a relationship by ID' uses a specific verb ('get') and resource ('relationship'), with the scope clarified by 'by ID'. It clearly distinguishes from sibling tools like listRelationships, createRelationship, and updateRelationship, which have different actions.

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 listRelationships. There is no mention of prerequisites, exclusions, or direct comparisons, leaving usage to pure implication.

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