findDefinition

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

With no annotations, the description must convey behavioral traits. It only states 'Find symbol definition', with no mention of return behavior, whether it's read-only, error handling, or any side effects. This is minimal disclosure, though it implies a read operation.

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?

At only three words, the description is extremely terse but under-specified. It lacks the necessary structure to prepare an agent for invocation. This is under-specification rather than effective conciseness.

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 tool has 7 parameters and no output schema, requiring a rich description. The given text offers no information about input requirements, optional parameters, output format, or behavior, making it inadequate for reliable invocation.

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 description coverage is 0% and the description provides no explanation of the seven parameters (url, source, line, startCol, endCol, mainProgram, implementation). The description does not compensate for the sparse schema, leaving parameter semantics completely unexplained.

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 'Find symbol definition' clearly identifies the tool's core function (locating a definition for a symbol), but it provides no differentiation from siblings like 'findObjectPath' or 'objectStructure'. The verb+resource is specific enough for a basic understanding, but lacks scope details.

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 versus alternatives like 'usageReferences' or 'searchObject'. The description contains only the operation name, with no context, prerequisites, or exclusion criteria.

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