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

No annotations are provided, so the description carries the full burden. It discloses that the tool returns full text content and supports two input modes (catalog discovery or topic search). Missing are details on failure behavior, output formatting, and any auth/network requirements, but for a read-only tool the disclosed behavior is reasonably adequate.

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, front-loaded with purpose and return type, followed by usage guidance. Every phrase earns its place and nothing is wasted.

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 simple (one required parameter, no output schema, no nested objects), and the description covers core behavior, return value, and discovery workflow. Minor gaps like failure behavior and exact output formatting keep it from a 5, but for the tool's complexity it is largely 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?

The schema already fully documents the single 'topic' parameter with examples and the slug alternative (100% coverage), so the baseline is 3. The description adds value by recommending the catalog resource first to find valid slugs, which slightly enriches parameter guidance, but does not fundamentally extend what the schema already provides.

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?

States a specific verb 'read' and resource 'PostCopilot blog post/guide about Threads', and immediately clarifies the return value ('Returns the full text content'). This clearly differentiates from sibling tools, which are all distinct actions like download_video, export_followers, and generate_post.

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?

Gives explicit workflow guidance: use the postcopilot://blog/catalog resource first to see available guides, or provide a topic to search. This tells the agent how to discover valid input values. It doesn't explicitly name alternatives to exclude, but sibling tools are all obviously different actions, so no exclusion is necessary.

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