imports

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

With no annotations, the description must convey behavioral traits, but it only states 'List imports'. It does not indicate whether the operation is read-only, has side effects, or requires specific permissions. The behavior is implied but not explicit.

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 short. While it earns its place by stating the purpose, it lacks structure and additional context that could be added without much length.

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 has three required parameters and no annotations, the description is incomplete. It does not explain what 'imports' are, what the output contains beyond the schema, or any constraints. An output schema exists but does not compensate for missing context.

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 100%; each parameter has a minimal description (e.g., 'Offset', 'Count (0=all)'). The tool description adds no additional meaning beyond these, so baseline 3 is appropriate.

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 'List imports' provides a verb and resource, but is vague; it does not specify what 'imports' refers to (e.g., imported functions, modules) and lacks differentiation from numerous sibling list tools like list_funcs or list_globals.

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 given on when to use this tool versus alternatives, nor any context or exclusions. The description fails to help the agent decide between this and sibling listing tools.

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