abs_genres

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

Goes well beyond the annotations: it discloses the Bearer token source, self-hosted-only scope, the double gate on writes (confirm plus env flag), that a dry run sends nothing, that destructive/credential actions add an extra warning in the preview, and enumerates which of those actions are dangerous. This is exactly the context annotations cannot carry and is consistent with destructiveHint=true and readOnlyHint=false.

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?

Front-loaded with domain, auth, and scope, then the write-safety rules, then the action list. Dense but every sentence carries operational information; the destructive-action enumeration is a bit of a list but pays for itself in preview expectations.

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 multi-operation dispatch tool with nested objects, no output schema, and 100% schema coverage, the description supplies the missing pieces: auth, host scope, write gating, dry-run semantics, and a help action for per-action parameter discovery. An agent can invoke it correctly without opening any sibling definition.

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%, so baseline is 3; the description still adds value by explaining the action+target pairing for help and the runtime dependency (ABS_ALLOW_WRITES) that gates confirm. It adds little about body/params beyond what the schema already says, keeping it from a 5.

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?

Names the resource domain (genres), states the toolset size (3 operations), and enumerates the actions (delete_by_id, get, post_rename), which distinguishes it from siblings like abs_authors or abs_tags. The verbs stay at the action-name level rather than describing what each action retrieves or mutates, so it is clear but not maximally specific.

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 invocation rules: use action=help with target to learn an action's parameters, writes require confirm=true plus ABS_ALLOW_WRITES, and omitting confirm produces a dry run. It does not explicitly route the agent away from sibling toolsets, but for a namespaced CRUD wrapper that is largely self-evident.

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