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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=true, so the safety profile is covered. The description adds useful behavioral context beyond annotations: it notes the metrics:read requirement and that "Hosts that draw MCP Apps show it as a card," which tells the agent to expect app-style rendering. It does not cover rate limits or pagination, so it is strong but not exhaustive.

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?

The description is compact: one long sentence lists the returned contents, followed by a short usage cue and a rendering note. It is front-loaded with the substantive inventory, though the list is dense and a couple of terms ("honours," "publications left") could be tighter.

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, the description carries the burden of explaining what is returned, and it does so by enumerating the main data points (networks, posts, quotas, per-network views, best post, honours). Some terms remain vague, but for a no-parameter dashboard tool whose annotations already cover safety, this is adequately 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?

There are zero input parameters, so the baseline is 4. The description does not need to document parameter semantics, and the empty schema has 100% coverage for the absence of parameters. The parenthetical "(with metrics:read)" adds a permission-scope hint rather than parameter guidance.

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 names a specific resource (the account profile) and enumerates the concrete contents it returns: connected networks, published and scheduled posts, publications left, 30-day views per network, best post, and honours. It is clear what the tool does without opening a schema, though it does not explicitly contrast itself with siblings like whoami or get_metrics.

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 implied rather than stated. The phrase "The answer to 'how is my account doing?'" signals the question it addresses, but there is no explicit when-to-use guidance, no when-not to use it, and no named alternative such as whoami or get_metrics for narrower questions.

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