Registered connectors (?catalog=true: all)

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

Annotations already declare readOnlyHint and openWorldHint, so safety is covered. Beyond that the description adds only the endpoint path; it does not say whether results are paginated, scoped to the current workspace, or what 'catalog=true' actually changes behaviorally.

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?

It is short and front-loaded, but the one sentence is largely redundant with the title and the '?catalog=true: all' fragment is telegraphic rather than informative. There is no wasted length, but also almost no content.

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?

For a simple list tool this could be adequate, but with no output schema the description should describe the shape of returned connectors, and with a 0%-covered parameter it should explain the catalog toggle. Neither is present, and the relationship to sibling list endpoints is unstated.

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 description coverage is 0% for the single 'catalog' enum parameter, so the description carries the full burden. The cryptic '?catalog=true: all' at least implies true returns all connectors, but it never explains the false/default behavior or the string-typed boolean convention.

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 text is a verbatim restatement of the title plus the HTTP route (GET /v1/platforms), so the only real content is 'list platforms/connectors'. There is no verb phrase and no differentiation from the many sibling list tools (connections_list, adAccounts_list, clients_list), so an agent cannot tell what a 'platform' is here.

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?

No when-to-use guidance and no named alternative. The fragment '?catalog=true: all' hints that the flag widens the result set, but it never states when to set it or what the default (false) returns, so the choice between the two modes is left to guesswork.

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