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

Adds real context beyond the annotations: private metadata is preserved on title/subject/tag edits, a distinct manage:library grant is required, confirmation gating is enforced, and no customer credits are debited. It never explains why destructiveHint=true is set — notably whether supplying tags replaces the existing tag set or merges — which is exactly the risk an agent needs spelled out.

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?

Four tight sentences, front-loaded with the operation, then preconditions, then the id source, then the cost note. Nothing is repeated from the title or schema, and each sentence adds new information.

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 mutating tool with no output schema and zero schema descriptions, it covers permissions, confirmation, parameter provenance and credit side effects. Still missing: what the call returns, failure modes (grant missing, confirm omitted), and the tag-set replacement semantics implied by destructiveHint=true.

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%, so the description must carry the load; it names all five parameters and gives meaning to two of the trickiest (assetId provenance via soclo_library_search, confirm gating after owner approval). It does not convey the tag enum vocabulary, the 6-item cap, or the length limits, and does not disambiguate replace-vs-merge for tags.

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 pair and resource with scope: 'Rename or tag one selected owned Library item'. The scope words 'one selected owned' plus the field list (title, subject, tags) separate it cleanly from soclo_library_upload, soclo_library_delete, soclo_library_search and soclo_library_finalize without the agent opening any schema.

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 concrete preconditions: needs the separate manage:library grant, requires confirm: true after owner approval, and assetId must come from soclo_library_search. It stops short of naming when NOT to use it (e.g. bulk edits or non-owned items handled elsewhere), so it is strong but not exhaustive.

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