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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so the 'Read-only' clause is partly redundant. However the description adds genuinely new behavioral context: zero credit cost, that the integration summary contains 'no secrets', and the shape of the returned post data. That is useful beyond the annotations, though not exhaustive about failure modes (e.g. behavior when no blog is connected).

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?

Roughly three dense sentences that are front-loaded with the return contract, then the routing guidance. Slight redundancy in restating read-only behavior that annotations already cover, but no filler.

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?

The tool is low-complexity with zero parameters and an output schema, so return values need not be enumerated. The description nonetheless summarizes the key outputs and states the credit/auth implications, which is complete enough for an agent to call it correctly on the first try.

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 nothing for the description to disambiguate; the schema-level baseline of 4 applies. The description correctly implies a no-argument call by describing only team-scoped output.

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 compound verb+resource: check WordPress blog connection and fetch the latest post snippet. It clearly separates this from siblings like test_blog_connection and create_blog_plan by naming what it returns (blogConnected, integration summary, latest post title/snippet/status/URL).

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 gives an explicit precondition: 'Use before create_blog_plan or test_blog_connection to see if a blog is wired up and what was last published.' Both the alternative tools and the selecting condition are named, leaving nothing to inference.

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