Symbol Context

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the tool is known to be read-only. The description adds the 'REPO-ISOLATED' behavior, but does not disclose other traits like response format, error handling, or rate limits. It adds minimal value beyond 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 extremely concise at one sentence. It is front-loaded with the primary purpose. However, it is perhaps too sparse, missing opportunities to add structure or list parameters.

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?

With no output schema and a brief description, the tool lacks crucial context. There is no information about return values, pagination, error cases, or usage examples. For a tool with 4 parameters and no schema descriptions, the description is incomplete.

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%, meaning the schema has no parameter descriptions. The description partially compensates by listing 'Callers/callees/tests' which maps to the 'what' parameter enum values. However, it provides no explanation of the other parameters (symbol, filePath, repository_id), leaving them undefined.

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 the tool returns 'Callers/callees/tests for a repository.' This is a specific verb+resource combination. However, it does not explicitly differentiate from sibling tools like 'context.expand' or 'symbol.source', though the 'REPO-ISOLATED' hint provides some distinction.

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?

There is no guidance on when to use this tool versus alternatives like 'context.expand' or 'symbol.source'. The phrase 'REPO-ISOLATED' implies a scope constraint, but no explicit when-not or alternative tool references are provided.

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