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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description then adds real value by spelling out the six things returned (connections, clients and their links, next setup step, example prompts, 30-day feature list), which compensates for the absent output schema — though it says nothing about payload format or size.

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 sentences, no filler: the trigger condition leads and the return payload follows. Every clause carries information an agent would otherwise have to guess.

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 parameterless, read-only, closed-world tool with no output schema, the description supplies both the invocation trigger and the full expected return content. Nothing needed to select or call it correctly 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?

With zero parameters and 100% schema coverage, there is nothing for the description to disambiguate at the parameter level. Its decision-relevant content (which agency, what is returned) is handled elsewhere in the text, so the baseline of 4 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 gives a specific role — an onboarding/status aggregator that returns connected platforms, clients and their links, the next setup step, example prompts, and recent features. That enumeration distinguishes it from near-neighbours like whoami, list_clients, and whole_picture without needing to open any schema.

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?

It opens with an explicit trigger sentence covering four user intents ('how to set up Agency Autopilot', 'what it can do', 'what is new', 'what to do first'), which is exactly the decision signal an agent needs. It does not, however, name a competing sibling or state when not to use it, so it falls short of a full 5.

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