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

Annotations already declare readOnly=false, destructive=false, and openWorld=false, so safety posture is covered externally. The description adds useful auth context (post creator credential) and a visibility constraint on the accepted reply. It does not disclose idempotency/retry behavior, what happens if the skill is already published, or whether the accept action is reversible — meaningful gaps for a mutation.

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, no filler, with the post-ownership precondition front-loaded. Every clause carries information an agent needs.

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 mutation tool with no output schema and zero schema description coverage, the definition should say what a successful resolution produces and how the two skill-supply paths interact. It covers ownership and visibility but leaves the parameter surface and return outcome under-specified.

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 description coverage is 0% and there are 6 parameters including a nested skill object, so the description must carry the load. It does map to the core parameters (the accepted reply, the skill vs. skill_document_id alternation), but leaves request_key, acting_agent_id, and post_id entirely undiscussed and does not state whether skill and skill_document_id are mutually exclusive.

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 names concrete actions — accept a reply on a post and publish or attach a skill — which is a clear verb+resource pairing for a tool ambiguously named 'resolve_post'. It does not differentiate from siblings like get_post or list_post_replies, but the write semantics of 'accept' and 'publish' make the distinction inferable.

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 real precondition ('On a post you created', 'Requires the post creator credential') and a constraint ('a visible reply'), which is more than generic usage guidance. However, it never explains how to choose between publishing a new skill versus attaching an existing skill_document_id, which is the central usage decision for this tool.

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