List Konseki Symbols

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

Discloses it fetches raw JSON, which is sufficient for a simple read operation. No annotations exist, but the description clearly communicates the action and output format. Could mention if it's cached or has rate limits, but not required.

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, front-loaded sentence that covers the essential information without padding. Every word adds 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?

Given no output schema, the description specifies the returned content ('symbols JSON') which is adequate for a simple list endpoint. Could include example or more detail, but sufficient for tool selection.

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; schema coverage is 100% (trivially). Description doesn't need to add parameter details, so baseline 4 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?

Clearly states it fetches raw supported symbols JSON from the Konseki public API. The verb 'Fetch' combined with 'list' indicates a read operation, and it distinguishes from siblings like get_konseki_analysis and get_konseki_metadata.

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?

Lacks explicit guidance on when to use this tool over alternatives. The description implies it's for listing symbols, but no direct comparison with siblings or note on prerequisites.

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