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

Annotations already declare destructiveHint=true, readOnlyHint=false, and idempotentHint=false, so the mutation risk is covered. The description adds real context beyond that: requests are authenticated, and access is limited to /v1 and /api paths with admin surfaces excluded. It stops short of describing error behavior or rate limits, so not a 5.

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 tight sentences with zero filler; the operation and its scope constraint are both front-loaded. Nothing in the text is redundant with the schema or annotations.

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 generic authenticated write proxy with no output schema, the description covers the write methods and the reachable path space, which is the minimum an agent needs. It omits anything about response shape, error handling, or how credentials are supplied, leaving real gaps for a tool this broad.

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 75%, so the schema already documents body, path, query, and the method enum. The description's mention of the three methods and the /v1 or /api path prefixes reinforces the two required parameters but adds no format, syntax, or example detail beyond the schema. Baseline 3 is appropriate.

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 set (POST/PATCH/DELETE) and resource (AffixIO /v1 or /api endpoint) in one clause, immediately distinguishing it from the read counterpart affix_api_read. The added scope note about excluded administration paths sharpens rather than muddies the purpose.

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 explicit negative scope ('Account, key, OAuth and webhook administration paths are not exposed'), which tells the agent when this tool will fail. It doesn't name affix_api_read as the alternative for GET, but the read/write split is unambiguous from the verb list.

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