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

Annotations already declare readOnlyHint=false, destructiveHint=false, and idempotentHint=true. The description adds useful context beyond those hints by spelling out the upsert behavior and the authentication requirement. There is no contradiction between the description and the annotations.

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 three short sentences, each carrying information: the save action, the upsert behavior, and the auth requirement. The key verb and object are front-loaded with no filler or redundant elaboration.

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?

Given the very rich input schema and the annotations, the description covers the essential behavioral points: persistence target, upsert behavior, and authentication. It omits return/error details, but with no output schema and a fully documented input schema, this is a minor gap for a straightforward save operation.

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 100%, with token documented as 'Your Rhylthyme access token' and program described as 'Rhylthyme program JSON. Read rhylthyme://guide/authoring for the rules.' The description adds little beyond what the schema already provides, so the baseline of 3 is appropriate.

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?

The description opens with the verb 'Save' and a specific resource: 'a Rhylthyme program to your account,' so an agent immediately knows the action and target. It also clarifies upsert semantics ('if a program with the same programId already exists, it will be updated'), which distinguishes it from generic imports or loads. This is unambiguous even among the sibling tool list.

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?

The description provides clear operational context: save is for persisting a program to the caller's account, and it states the prerequisite 'Requires a login token.' It does not explicitly name alternatives or when-not-to-use cases, but the save-to-account framing is sufficient to guide tool selection.

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