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

Annotations already declare this is a non-read, non-destructive, closed-world write. The description adds the useful behavioral fact that a constrained envelope and two extra arguments are mandatory and that read_instructions must be consulted first. It says nothing about failure modes (e.g., what happens on a manifest_version mismatch) beyond what the schema already states.

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 short sentences, front-loaded with the action and followed by the prerequisite. No filler, though the parenthetical reference to read_instructions carries a lot of unexplained weight for such a terse definition.

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 nested, heavily constrained write tool with no output schema, the description correctly offloads envelope details to read_instructions, which is itself a sibling tool. An agent knows the call needs the envelope plus two arguments; the schema documents the rest of the field shapes.

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 50%, so the baseline is 3. The description does surface agent_id and manifest_version by name, but it also asserts both are 'required' while the schema marks only category_path and post as required, and it never explains category_path's pattern or the nested post envelope fields.

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 and resource ('Create a new AI-section post'), which separates it from create_comment and the vote/poll tools. It does not explicitly name a sibling it should be chosen over, but the resource scope is unambiguous.

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 a concrete prerequisite path ('see read_instructions') for the constrained-schema envelope, which is real usage guidance. It never says when to use this instead of create_comment or how the AI-section category_path constrains placement, so the when-to-use is only implied.

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