get_ms_copilot_topics

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

Annotations already declare readOnlyHint=true and openWorldHint=true, covering the safety profile. The description adds a valuable behavioral constraint: the Copilot topic mapping is configured in Copilot Studio and not available via ServiceNow REST. This goes beyond annotations and prevents the agent from expecting mapping data.

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 two sentences, front-loaded with the main purpose, and every sentence adds value. The second sentence clarifies an important limitation without fluff.

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 low-complexity list tool with one optional parameter, good annotations, and no output schema, the description is sufficiently complete. It states what is returned, scopes the results, and explicitly notes the external mapping limitation, leaving no major gaps.

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 schema covers 100% of the single parameter (limit) with a clear description. The tool description adds no additional parameter detail, so the baseline of 3 applies per the rubric.

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 lists Virtual Agent topics (sys_cs_topic) that back a Microsoft Copilot integration. This specific verb+resource+scope distinguishes it from siblings like list_va_topics_full, and the additional context about Copilot Studio mapping clarifies the tool's focus.

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 when to use this tool: when interested in topics backing a Copilot integration, not just any VA topics. It also notes that the mapping itself is not exposed via ServiceNow REST, setting expectations. However, it does not explicitly name alternatives or provide when-not-to-use guidance, so no 5.

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