rec_profile_save

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

Annotations already declare readOnlyHint=false, idempotentHint=true, and destructiveHint=false. The description adds useful behavioral detail about source combination, mode='auto' selection rules, and that triggers/default cycle are stored, but it omits what happens to an existing profile with the same name when replace defaults to true.

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?

The description is front-loaded with the main action and packs a lot of technical detail into one dense paragraph. It is not wasteful, though the parenthetical syntax makes it less scannable than a bulleted breakdown would be.

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 13-parameter tool with 0% schema description coverage, the description is incomplete: several parameters and the replace/overwrite behavior are not explained. An output schema exists and annotations cover safety, but the description still leaves important invocation details to inference.

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 0% with 13 parameters, so the description must compensate. It explains mode, symbols, from_checklist, from_attributes, and scope, but leaves replace, duration_s, start_when, stop_when, pre_trigger_ms, description, and cycle_ms (beyond 'default cycle') undocumented.

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: 'Save a named capture profile.' It distinguishes itself from siblings by naming rec_profile_start for replay and rec_scan as a source for checklists, so an agent can tell what this tool is for.

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 how source selection works and points to rec_scan for checklist names and rec_profile_start for replay. It does not explicitly state when to use this instead of directly starting a recording, but the context is clear enough for selection.

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