Remember Song

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

With no annotations provided, the description carries the full burden of behavioral disclosure, but it only states that a SongSpec is remembered. It does not explain whether this persists data, overwrites existing entries, requires prior context, or has side effects, which is a significant gap for a storage operation.

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 a single, front-loaded sentence with no filler or redundancy. It is concise and easy to parse, though it sacrifices useful behavioral and usage context for brevity.

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 tool with nested open-object parameters and no annotations, the description is too thin to give an agent full confidence in when and how to invoke it. The output schema may cover return values, but the description still lacks context about the role of this tool in the broader song workflow and the meaning of 'remember' in this domain.

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%, so the description must compensate for the lack of parameter documentation. It identifies 'songspec' as the required value and 'review' as optional, which adds marginal meaning, but it does not describe the shape, purpose, or constraints of the nested objects.

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 states a specific action ('Remember') and a clear resource ('a SongSpec and optional ReviewResult'), which conveys the tool's storage purpose. It is distinguishable from siblings like generate_songspec, review_songspec, and search_memory, though it does not explicitly name its relationship to them.

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 gives no guidance on when to use this tool versus alternatives such as search_memory or create_project_from_songspec. There are no stated conditions, prerequisites, or exclusions, leaving the agent to infer usage solely from the verb 'remember'.

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