list_publishing_connections

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

No annotations are provided, so the description carries the burden. It clearly indicates a read-only listing operation and gives context about the types of connections. However, it does not disclose any behavioral details like whether it returns empty results, requires an existing publication, or pagination. For a simple list tool, this is adequate but not rich.

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?

Single sentence, front-loaded with the verb and resource, no filler. Efficient and to the point.

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?

The tool is low complexity (2 params, no nested objects) and the description explains what it lists. No output schema exists, but the description's examples clarify the domain. It could hint at return details, but for a simple list it is sufficiently 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?

Both parameters are documented in the schema with clear descriptions (publicationId as 'Blog publication ID', brandId as 'Brand ID (uses active brand if omitted)'). The description does not add additional parameter semantics beyond confirming the connection types. Schema coverage is 100%, so the baseline of 3 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 uses the specific verb 'list' and resource 'external publishing connections' for a blog publication, with concrete examples (WordPress, Medium, Substack). This clearly distinguishes it from sibling tools like list_publications or list_blogs.

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 it: when you need to see external publishing connections for a specific blog publication. However, it does not explicitly state when not to use it or mention alternative tools, leaving usage guidance implicit.

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