pubsub_list_topics

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

With no annotations, the description must carry the behavioral burden, and it does disclose the shape of the response: counts, subscriptions, and triggered functions, with schedule topics included. It never states that this is a read-only, side-effect-free listing, nor anything about ordering, pagination, or what an empty emulator returns.

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?

A single dense sentence with no filler, front-loaded on the resource and immediately followed by the returned fields. The trailing parenthetical about schedule topics is slightly awkward but earns its place by defining scope.

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?

There is no output schema, so the description has to describe return values, and it does so only at a high level: field names without types or structure. For a simple zero-parameter lister this is close to adequate, but it leaves the agent guessing about the nesting of subscriptions and trigger functions.

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 tool takes zero parameters and the schema is an empty object with additionalProperties false, so there is nothing for the description to clarify. The baseline for a no-parameter tool applies.

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 names the resource precisely (the Pub/Sub emulator's topics) and enumerates what comes back: published counts, subscriptions, and the functions each topic triggers. It also marks its scope against sibling listing tools by noting that schedule topics are included. It loses a point only because it is a noun phrase with no explicit verb like 'list'.

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?

There is no when-to-use guidance and no mention of alternatives such as pubsub_list_subscriptions, pubsub_peek, or schedules_list. The scope note about schedule topics hints at coverage but does not tell an agent which sibling to choose for which question.

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