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

Annotations cover safety/idempotency, and the description adds substantial context beyond them: each run reserves credits, runs pause when funding/authority/expiry/limits disallow work, the quoted maximum is reserved from prepaid credits, the matching action scope is required for auth, and sandbox execution is simulated. This is exactly the operational detail annotations cannot convey.

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?

Purpose is front-loaded and no sentence is pure filler, but the block is dense and slightly muddled: it says 'Returns monitor_id' and later 'returns operation_id; poll get_operation', which leaves the agent unsure which identifier it receives. The credit-reservation point is also restated near the end.

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 complex, credit-consuming enrollment tool with no output schema, the description covers prerequisites, auth scope, budget/expiry behavior, pausing conditions, sandbox simulation, and result polling. Minor gaps remain on how it interacts with pause_monitor/resume_monitor and on the monitor_id vs operation_id confusion.

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 quote_id and idempotency_key are already documented. The description adds the useful point that all task input lives inside the quote (rights_holder_id, work_id, delegation_id, target_action, expires_at, limits, handles), but this elaborates the quote's contents rather than either parameter's own semantics. Baseline 3.

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 ('Enroll recurring search or case-status observations') and immediately scopes it with budget and expiry. An agent can distinguish it from get_monitor, pause_monitor, resume_monitor, and create_quote without 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 clear prerequisites: call create_quote(action='monitor') first, supply main_handle for target_action='search' or case_id for 'status', and poll get_operation for results. It also states a boundary ('Never schedules takedown submissions'), but does not explicitly say when to prefer pause_monitor/resume_monitor or when not to enroll at all.

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