check_symbol_conflicts

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. It clearly states the tool performs a check and returns a report with disambiguation suggestions. It does not indicate any destructive side effects, and the behavior (read-only inspection) is well communicated.

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 extremely concise: three short sentences with no wasted words. It front-loads the core action with a warning emoji, defines key terms, and states the return value. Every sentence adds 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?

Given zero parameters and the presence of an output schema, the description is largely complete. It explains the tool's purpose and output. However, it could briefly mention when in the workflow this check is relevant, but that is a minor gap.

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 tool has zero parameters, so by guidelines the baseline is 4. The description does not need to add parameter semantics, and it correctly omits them. The empty input schema is fully covered.

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 clearly states the tool's purpose: checking for ambiguous symbols in the current session. It defines what a conflict is (same symbol name with multiple meanings or domains) and mentions the return type (conflict report with suggested disambiguation). This is specific and distinguishes it from sibling tools like check_assumption_conflicts and other symbol-related tools.

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 you need to detect symbol ambiguity but does not explicitly state when to use this tool versus alternatives like check_assumption_conflicts or list_domain_symbols. There is no guidance on when not to use it or prerequisites, leaving the agent to infer context.

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