buscar_simbolo

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

With no annotations, the description carries the full burden of behavioral disclosure, but it only states the tool's purpose. It does not reveal whether it returns a file path, line number, multiple locations, or what happens for missing symbols, leaving the agent to guess at the tool's runtime behavior.

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 a single, front-loaded sentence that wastes no words. It clearly conveys the operation without over-explaining.

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 one-parameter, no-output-schema tool, the description is adequate but lacks detail about the return format and edge cases. It doesn't explain the result structure (e.g., file path, line number), which an agent would need to correctly consume the output, but the simplicity keeps this from being a major 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 input schema already documents the single parameter 'nombre' as the exact symbol name (100% coverage). The description adds context by specifying the symbol is an exported TypeScript/React symbol, which clarifies the parameter's domain, but this is nominal added value beyond the schema.

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 a specific action and resource: it finds where an exported TypeScript/React symbol is defined. This distinguishes it from sibling tools like buscar_texto (text search) and buscar_referencias (references) by its focus on definition location, though it doesn't explicitly name those alternatives.

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 intended use is implied by the description: use it when you need to locate the definition of an exported symbol. However, there is no explicit guidance about when not to use it or which sibling tool to choose instead.

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