find_element

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

Discloses matching precedence (exact ID first, then exact name/serial/hw_id case-insensitive, then substring), never auto-picks multiple hits, includes site_id when available, and explains pagination semantics. This goes well beyond the readOnly/idempotent hints provided in 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?

The description is well-structured with a lead sentence and focused sections, but the Args block repeats parameter descriptions already present in the schema. This is slightly redundant but not excessive given the tool's 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?

The description fully covers usage behavior, ambiguity handling, pagination, and return context (site_id). With output schema available and strong annotations, the description is complete for an agent to 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?

Schema coverage is 100%, and the description's Args section essentially mirrors the schema's parameter descriptions verbatim. It adds no new parameter-level detail beyond the schema, so the baseline 3 applies.

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 opens with a specific verb and resource: 'Resolve an ION/element name or exact ID without guessing.' It clearly distinguishes this tool from siblings like find_site or find_resource by focusing on element resolution and ID matching behavior.

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 clear procedural guidance: omit cursor on first call, use limit to page, and re-call with a more specific value or exact ID when ambiguous. It doesn't explicitly name alternative tools, but the intended usage context is unambiguous.

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