servicebus_list_topics

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

With no annotations, the description carries full burden. It discloses return format (sorted JSON array, optionally with subscriptions), namespace format flexibility (short name or FQDN), and authentication behavior (connection string vs DefaultAzureCredential). Minor gaps: no mention of errors or rate limits.

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 concise with two well-structured paragraphs. First paragraph states purpose and behavior, second paragraph details the environment variable parameter. No redundant information; every sentence 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 the output schema exists, the description still provides sufficient details about return format and options. All critical aspects (parameters, behavior, auth) are covered. The tool is straightforward and the description leaves no major gaps for an agent.

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 0%, so description must add value. It provides meaning for all three parameters: namespace (short name or FQDN), include_subscriptions (triggers mapping return), connection_string_env_var (env var name and auth fallback). This compensates well for lack of schema descriptions.

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 'List all topics in an Azure Service Bus namespace' with a specific verb and resource. It distinguishes from siblings like servicebus_list_queues by focusing on topics, and describes return format options (sorted JSON array or mapping with subscriptions).

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 (listing topics) but provides no explicit guidance on when not to use or alternatives. No contrast with sibling tools such as servicebus_list_queues or servicebus_list_namespaces is given.

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