search_memento_relationships_by_context

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

No annotations provided, so description carries full burden of behavioral disclosure, but offers none. Does not confirm read-only safety despite 'search' implying it, describe return format/pagination, explain result sorting, or mention any limits beyond the parameter constraint.

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?

Single sentence efficiently front-loaded with action and resource. Lists key filter fields concisely. No wasted words, though brevity may be excessive given the lack of annotations and output schema—slightly too terse for the complexity.

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?

Incomplete for a 7-parameter search tool with no annotations and no output schema. Description omits what distinguishes a 'relationship' from a 'memento', what fields are returned, result ordering, and how results relate to the 'temporal' filter. Lacks critical context for confident invocation.

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?

With 100% schema description coverage, the schema already documents all parameter semantics (e.g., 'Filter by scope', 'Matches any'). Description lists the fields parenthetically but adds no additional meaning, examples, or syntax guidance beyond the schema. Baseline 3 is appropriate.

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?

Clear verb (search) and resource (memento relationships) with specific enumeration of filterable fields (scope, conditions, evidence, components). Distinguishes from sibling 'search_mementos' by targeting relationships rather than mementos themselves, though could explicitly clarify the distinction from 'contextual_memento_search'.

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?

Provides no guidance on when to use this tool versus siblings like 'search_mementos', 'contextual_memento_search', or 'get_related_mementos'. Does not mention that all parameters are optional or suggest combinations for common queries.

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