list_all_topics

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

With no annotations, the description carries full burden for behavioral disclosure. It only states the tool returns a list, with no mention of side effects, permissions, rate limits, or whether the operation is read-only. The agent lacks critical behavioral context.

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 that efficiently conveys the tool's action and result. It is front-loaded with the key verb 'Returns' and immediately specifies the resources. No redundant words; every word earns its place.

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 no parameters, no output schema, and no annotations, the description is the sole source of information. It adequately explains the high-level purpose but lacks details such as return format, pagination, authentication requirements, or potential performance implications. For a simple list retrieval, it is minimally acceptable but not fully complete.

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?

The input schema has zero parameters, so schema coverage is trivially 100%. Baseline for 0 parameters is 4. The description adds value by explaining what the tool returns, which is essential since the schema provides no structure. However, it could be more precise about the exact fields or types returned.

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 tool returns a full list of frameworks, questionnaire topics, RFP sections, and battlecards. The verb 'Returns' and the specific resources make the purpose clear. However, the tool name 'list_all_topics' is narrower than the description, which could cause slight confusion. Still, it effectively distinguishes from siblings that retrieve single items.

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 provides no guidance on when to use this tool versus alternatives. It does not mention exclusions, prerequisites, or scenarios where other sibling tools might be more appropriate. The agent receives no context for decision-making beyond the basic purpose.

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