list_publications

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

Describes as 'Deterministic' and enumerates the output details (per-table column lists, row filters, operations). With no annotations, the description carries the full burden; it implies read-only behavior but does not explicitly state safety.

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?

Two short, front-loaded sentences with no wasted words. Every sentence provides essential information.

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 no parameters and an output schema exists, the description sufficiently covers the listing task. It could mention that it is a safe read operation, but overall 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?

No parameters exist, so schema coverage is 100%. The description adds value by explaining what information is listed, which goes beyond the empty schema.

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?

Clearly states 'List publications and the tables each carries', which is a specific verb+resource. Distinguishes from siblings like 'check_publication_coverage' and 'inspect_subscriptions' by detailing the contents (tables, columns, filters, operations).

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?

Advises to 'Run this on the PUBLISHER', providing location guidance. However, it does not explicitly compare to alternatives or state when not to use, missing opportunities for clearer decision-making.

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