katto_list_connected_accounts

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

Annotations already declare readOnly/idempotent/non-destructive, and the description goes well beyond them: it describes the return shape, semantics of reconnect_required, the connect_url remediation path, and explicitly rules out token exposure. That is meaningful behavioral context an agent needs for a pre-publish safety check.

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?

Front-loaded with 'Read-only' and a single dense sentence that earns its clauses; nearly every element carries decision-relevant information. Minor redundancy: 'Read-only' restates the readOnlyHint annotation and could be dropped.

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?

With no output schema and no input parameters, the description fully carries the burden and does so: it specifies the returned fields, the platform set, and the failure-mode handling. Nothing an agent needs to call and act on this tool is missing.

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, so the baseline is 4; there is nothing for the description to compensate for. The description's mapping of return fields is a bonus rather than a parameter explanation.

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?

States a specific verb (list) and resource (connected accounts across 7 named platforms) and clarifies the scope is the Katto dashboard. The enumerated platform list and field set make it impossible to confuse with sibling readers like katto_get_account or katto_list_sources.

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?

Explicitly prescribes ordering ('Call it BEFORE katto_publish_clip') and names the alternative action when the target platform shows connected=false or reconnect_required=true, directing the agent to connect_url rather than attempting a publish. This is exactly the when/when-not/alternative guidance the dimension asks for.

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