org_endpoint_external_references_search

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

With no annotations, the description must fully disclose behavioral traits. It states it returns events but does not mention read-only nature, pagination, rate limits, authentication, or response format. The required params hint at behavior but are contradicted by the schema.

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 very short (one sentence) but includes redundant endpoint path. It is concise but not well-structured; it fails to front-load the most critical information about purpose and usage.

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 the absence of annotations and output schema, the description is severely incomplete. For a search tool with 7 parameters, it should explain return values, pagination, and how parameters affect results.

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?

Schema coverage is 100% but descriptions are minimal ('query param X (type)'). The description adds that q, from, and size are required, but the schema marks them as optional with default null, creating a contradiction. This misleads the agent about parameter necessity.

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 states it returns events via a search endpoint, but it does not specify what kind of events (external references) clearly. The tool name includes 'external_references_search', but the description uses 'events' without linking to the resource. It is somewhat clear but lacks specificity to distinguish it from similar sibling search 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?

No guidance is provided on when to use this tool instead of alternatives like endpoint_search or external_reference_external_references_search_by_fields. The description does not mention any context, prerequisites, or exclusions.

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