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

Goes well beyond the destructiveHint=false/readOnlyHint=false annotations: it discloses the partial-write semantics (other fields untouched), that no historical data exists for newly added actions, the 40-entry cap, and why the cap exists (every tracked id becomes a key read on every request). This is exactly the kind of consequence-level context a mutation tool needs.

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-loads the critical 'PARTIAL SAVE' constraint before explaining the domain concept, and every sentence carries information. Slightly repetitive with the schema in re-stating the 'Character:EquipItems' example and the case-insensitivity, which keeps it from a 5.

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?

With no output schema, the description carries the full burden and does so: it covers write scope, cap, temporal behavior of new entries, and the analytics purpose. An agent has everything needed to call it correctly against the 2-parameter nested schema.

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 already 100% with nested Actions/Enabled descriptions, so baseline is 3; the description adds real meaning on top by giving the entry format 'Character:EquipItems' (module from route + action name), the 40-entry limit, and the per-entry document-key cost that explains why the limit matters.

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 precise verb+resource+scope: 'PARTIAL SAVE: writes ONLY the FeatureTracking field of TitlePublicConfigurationModel; all other v1/v2 fields stay untouched.' It then defines what feature tracking actually is (which concrete actions get their own line in FeatureUsage), which distinguishes it from the many sibling save_* config tools and pairs with get_feature_tracking.

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?

Explains the operative context: this is purely an analytics setting that makes actions selectable as steps in custom funnels, and tracking only begins when an action is added. It stops short of naming an explicit alternative (e.g. get_feature_tracking to read, or that this is not the place to change module-level usage) or a when-not condition, so it is clear but not fully routing.

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