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

Annotations already declare readOnlyHint, idempotentHint and non-destructive behavior, so safety is covered. The description adds genuine context beyond that: the tool returns an instructional method ('a skill to follow') that the agent is meant to apply, not raw data. It stops short of describing the return format or whether the content is cached, so a 4.

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?

It is front-loaded with the core purpose, and the parenthetical explanations of the three skills each carry distinct, necessary information. It is a dense run-on sentence, but virtually every clause earns its place; only minor tightening is possible.

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 single-parameter, read-only, idempotent tool with full schema coverage and no output schema, the description covers what it returns (a skill to follow) and when to use it. The only soft gap is the exact return shape, which is implied as instructional text rather than stated explicitly.

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% with a bare enum, so the baseline would be 3, but the description goes well beyond it by explaining what each enum value does: content-strategy plans a month, post-craft directs one post, content-critic reviews and returns exact fixes. This meaningfully disambiguates the single required parameter beyond what the schema 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?

The description states a specific verb+resource: it delivers oriiion's own method for social media content as a skill to follow, and it enumerates the three concrete skills with their intents. An agent immediately understands this loads guidance rather than data. It does not explicitly differentiate itself from siblings like generate_posts or edit_caption, so it falls short of a 5.

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 clear context: load the right one before planning, writing or judging content for this account, and follow it. That maps usage to content-workflow stages and tells the agent which enum value applies to which task. It does not name exclusions or alternative tools to avoid, so it is a 4 rather than a 5.

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