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

Annotations already declare readOnlyHint=false and idempotentHint=false, but the description adds genuinely new context: the admin-only authorization requirement with the exact failure mode (403) and the plain-language warning that every call creates a new client. It stops short of describing the response payload or what happens if a same-named client exists.

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?

Three compact clauses, front-loaded with the WRITE marker and the operation, then auth, then the duplicate-creation caveat. No filler and nothing buried.

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 create tool with no output schema, the description covers the operation, endpoint, authorization constraint, and non-idempotency risk, which is most of what an agent needs. It could add a note on the response (e.g., whether the new client ID is returned) but nothing essential is missing.

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 100%, so both parameters (name, archive) are already fully documented with defaults and length constraints. The description adds no parameter-level detail beyond what the schema provides, which is the expected baseline when the schema does the work.

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 client') and even pins the endpoint (POST /clients.json), which cleanly separates it from tick_get_client and tick_list_clients. An agent can identify the operation without opening the 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?

It gives a critical precondition (Tick administrators only, 403 otherwise) and warns that each call produces a new client, which implicitly tells the agent not to retry blindly. However, it names no alternative tool or the condition under which an agent should prefer an update or lookup instead, so usage guidance is implied rather than explicit.

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