codeCompletionElement

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states 'retrieves', implying a read-only operation, but does not disclose any behavioral traits such as required permissions, rate limits, side effects, or response format. This leaves significant gaps for a tool with 4 required 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 a single, efficient sentence with no wasted words, making it appropriately concise. However, it is under-specified rather than optimally structured, as it lacks necessary details for clarity and completeness.

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 (4 required parameters), lack of annotations, 0% schema coverage, and no output schema, the description is completely inadequate. It fails to provide essential context on purpose, usage, behavior, or parameters, making it insufficient for effective tool selection and 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?

The schema description coverage is 0%, meaning none of the 4 parameters (sourceUrl, source, line, column) are documented in the schema. The description adds no meaning beyond the schema, failing to explain what these parameters represent or how they should be used, which is critical for tool invocation.

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 'Retrieves code completion element information' restates the tool name 'codeCompletionElement' with minimal elaboration, making it tautological. It specifies a verb ('retrieves') and resource ('code completion element information') but lacks specificity about what distinguishes it from sibling tools like 'codeCompletion' or 'codeCompletionFull', leaving the purpose vague.

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 such as 'codeCompletion' or 'codeCompletionFull'. The description offers no context, prerequisites, or exclusions, leaving the agent with no usage direction.

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