linka-teach-list-artifacts

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

Describes tool as 'read-only', which hints at non-destructive behavior, but lacks details on authorization, rate limits, or any side effects. No annotations to supplement.

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?

Single sentence, concise. Could be expanded slightly but not overly verbose.

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?

Minimal for a list operation. No output schema, so description should indicate what the listing contains (e.g., names, IDs). Lacks completeness for an agent to understand the output.

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?

No parameters, so the description need not add parameter info. The schema coverage is 100%, and the description is sufficient for the zero-parameter case.

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?

Clearly states it returns a listing of Teach artifacts and is read-only. Differentiates from get-artifact (single) and explain-artifact (explanation) by implication, but not explicitly.

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 on when to use this tool vs siblings like linka-teach-get-artifact or linka-teach-explain-artifact. Missing context for selection.

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