apex_detect_relationships

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

Annotations already indicate a read-only, idempotent, non-destructive operation. The description adds only the scope ('between a list of tables') and does not disclose additional behavioral details such as detection methodology, limitations, or handling of invalid input. No contradiction with annotations.

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 with no redundant words; front-loads the core action and resource. Highly concise and well-structured.

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?

For a simple, read-only tool with one well-documented parameter and an output schema, the description is adequate. However, it could slightly clarify whether 'auto-detect' means potential relationships or existing constraints, and whether any prerequisites apply. Overall, sufficient for the task.

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 sole parameter 'tables' is fully described in the schema (100% coverage), including case-insensitivity. The tool description's 'between a list of tables' echoes the schema without adding new semantic information, so 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?

Description clearly states the tool's function: auto-detecting foreign key relationships among a provided list of tables. Uses a specific verb ('auto-detect') and resource ('FK relationships'), distinguishing it from sibling tools like apex_describe_table or apex_generate_from_schema.

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 implies usage when FK relationships need to be identified among given tables, but it provides no explicit guidance on when to prefer this tool over alternatives, nor any when-not-to-use conditions. No exclusions or alternative tool mentions are given.

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