Topic List

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and openWorldHint=true, so the safety profile is clear. The description adds the return structure (fields in items array) but does not disclose potential limitations like pagination, ordering, or maximum results. Moderate value added beyond annotations.

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 sentence plus the return structure, front-loaded with the core action and resource. Every word is efficient; no wasted content.

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?

The description provides the return fields, which is helpful given no output schema. However, it lacks details on default ordering, pagination, or maximum number of topics returned. Still fairly complete for a simple list tool.

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 coverage is 100% with a description for the symbol parameter. The tool description does not add significant meaning beyond the schema (only an example is provided in the schema). 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 clearly states 'Get discussion topics for a symbol', specifying the verb 'get' and the resource 'discussion topics', with a specific parameter 'symbol'. It distinguishes from sibling tools like 'topic_detail' (single topic), 'topic_create' (creation), and 'topic_search' (search), providing clear purpose.

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?

The description implies usage when you need topics for a symbol, but does not provide explicit guidance on when to use this tool versus alternatives like 'topic_search' or 'topic_detail'. No exclusions or context for alternatives are given.

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