scf_set_target_maturity

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

Annotations only say readOnlyHint=false and destructiveHint=false; the description adds real context the annotations lack — that this is a write requiring ADMIN role, and that null clears the override and its reason, reverting to inherited behavior. It does not cover response shape or audit implications, but the key behavioral facts are present.

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?

A single tight sentence with the write/admin qualifier front-loaded and the null-revert behavior in a trailing parenthetical. No filler, though the parenthetical alternative-tool pointer slightly crowds the core statement.

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 4-param write with full schema coverage and no output schema, the description supplies the missing pieces: auth requirement, inherit-vs-override semantics, and where domain targets live. Nothing critical is absent, though the interaction between reason and null (reason is cleared) is only implied.

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 the schema already documents level, reason, org_id, and scf_id in full detail. The description restates the level range and null semantics, adding emphasis but no information beyond the schema — the baseline 3 applies.

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 ('Override one control's target maturity'), scopes it to a single control, and names the sibling that handles domain-level targets (scf_update_org_settings). An agent can distinguish it from scf_set_control_materiality or scf_set_control_basis_override without opening a 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?

Explicitly says when to use it (override a single control) and describes the revert path (null to inherit the domain target again), plus the ADMIN role prerequisite. It points at scf_update_org_settings for domain-level targets but stops short of an explicit 'use X instead when...' routing statement.

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