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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, and the trailing 'Read-only' merely restates them. The description does add genuine behavioral context by separating `limits` (plan quota, publishing cadence, Handler slot allocation, platform limits) from `rate_limits` (Handler slot numbers) — a distinction an agent would otherwise get wrong — but says nothing about response size, freshness, or whether results are cached per connection.

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 front-loaded with the high-level purpose, which is good, but the middle section is a single dense run-on with nested parentheticals, and the clause 'limits keeps four apart (this account's plan quota, publishing cadence, Handler slot allocation and platform limits)' is awkward and hard to parse. The four-way enumeration could be formatted far more cleanly.

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 zero parameters, a full output schema, and strong annotations, the description carries little burden — yet it devotes most of its length to restating return fields the output schema already declares. The real gap is routing: with 33 siblings including get_help, get_plans and get_usage, the description never tells an agent which call answers which question.

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 there is no parameter meaning to convey and the baseline of 4 applies. The description correctly spends no space on argument semantics.

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 states a specific verb and resource — it 'returns a structured map of the FeedSquad MCP surface this connection offers' — and enumerates the map's contents (tool groups, entrypoints, platforms, limits, versions). That is enough for an agent to know this is a discovery/introspection tool, though it never names the overlapping siblings (get_help, get_plans, get_usage) to sharpen the distinction.

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?

Usage is only implied: the mention of 'primary_entrypoints (the most common starting tools)' hints this is a sensible first call, but there is no explicit when-to-use statement or exclusion against get_help, get_plans, or get_usage, which cover adjacent ground. An agent must infer the routing decision itself.

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