list_solution_articles

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

With no annotations, the description must disclose behavioral traits. It implies a read-only operation but does not mention pagination, return format, or the folder scoping that contradicts the phrase 'all solution articles'. The requirement for folder_id is a key behavior that is omitted, making the tool appear more global than it actually is.

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 concise sentence with no unnecessary words. It front-loads the core action, but it is so brief that it misses critical context, slightly reducing its structural value.

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?

For a tool with one required parameter and no output schema, the description is incomplete. It fails to explain that folder_id is necessary, what the output format might be, or any prerequisite steps (e.g., listing folders first). This is a minimal but insufficient description for an agent to use correctly.

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 does not compensate. The sole parameter folder_id is not explained at all; the phrase 'all solution articles' actively conflicts with the fact that a specific folder_id is required, providing misleading parameter semantics.

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 verb 'List' and the resource 'solution articles', which identifies the tool's high-level purpose. However, it does not mention that listing is scoped to a specific folder via the required folder_id parameter, which could confuse agents into thinking it lists all articles globally.

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 view_solution_article or list_solution_folders. The description lacks any context about prerequisites (e.g., knowing the folder_id) or when a list operation is appropriate.

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