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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, open-world), so the description's job is added context — and it delivers by describing the shape of the payload and the semantic distinction that 'authors is people' while 'links' are the blog's own accounts, which is what an unsigned blog has instead. It does not discuss truncation beyond the limit default, but that is minor against the annotation coverage.

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?

Purpose is front-loaded in the first clause and every sentence carries information the agent needs (scope, semantic distinction, slug source, downstream handoff to read_post). The sentences are dense and the middle clause about topics 'no other feed shares' is slightly tangential, keeping it from a 5.

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 must describe the return payload, and it does so concretely: metadata, people, external accounts, topics, recent posts, plus per-post slug and guid. It also covers the input provenance rule, so an agent has everything needed to call this correctly and chain into read_post.

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 coverage is 100%, so both parameters are already documented, and the description adds real meaning on top: the slug must be a directory slug obtained from search or list_feeds rather than the site URL, and the feed slug/guid pair returned per post is what read_post consumes. That is genuine semantic value beyond the schema text.

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 opening sentence names a specific verb+resource ('One blog or podcast') and enumerates exactly what comes back: metadata, authorship, links, topics, recent posts. It is clearly distinguishable from siblings like get_author or get_topic, and it explicitly ties itself to read_post, which needs the slug and guid this tool returns.

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 a concrete precondition for the key input: 'Use the slug from search or list_feeds, not the site's own URL,' which prevents a common failure mode. It stops short of stating when to prefer get_author / get_topic / get_openprofile instead, so it is clear but not fully routing.

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