findDefinition

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

No annotations are provided, so the description must fully disclose behavioral traits. It only states the action without detailing whether it's read-only, requires authentication, has side effects, rate limits, or error handling. This leaves critical behavioral aspects unspecified for a tool with 7 parameters.

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 with a single phrase 'Find symbol definition', which is front-loaded and wastes no words. However, this conciseness comes at the cost of underspecification, but structurally, it meets the criterion of being brief and to the point.

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 tool's complexity (7 parameters, no annotations, no output schema), the description is incomplete. It lacks essential details about purpose differentiation, usage context, behavioral traits, and parameter meanings, making it inadequate for effective agent invocation in a server with many sibling tools.

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%, so the description must compensate by explaining parameters. It adds no meaning beyond the schema, failing to clarify what 'url', 'source', 'line', 'startCol', 'endCol', 'implementation', or 'mainProgram' represent or how they interact, despite 7 parameters being present.

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' restates the tool name 'findDefinition' with minimal elaboration, making it tautological. It specifies the action (find) and target (symbol definition) but lacks specificity about what a 'symbol' entails or how it differs from similar tools like 'searchObject' or 'ddicElement' in the sibling list.

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. With many sibling tools like 'searchObject', 'ddicElement', and 'codeCompletion', the description fails to indicate context, prerequisites, or exclusions, leaving the agent without direction for tool selection.

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