project_dump_score_log

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

With no annotations, the description must disclose behavior itself. It usefully reveals that notes are captured even without recording and that the target is the selected pattern. However, it does not state whether existing pattern content is replaced, merged, or appended, nor whether the operation is undoable or what 'silent' affects.

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 compact sentence plus a short prerequisite sentence. It front-loads the core action and adds the key 'even without recording' qualifier without wasting words.

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 2-parameter tool with no annotations and no output schema, the description covers the main operation and the key prerequisite well. However, it omits side-effect semantics on the target pattern and the meaning of 'silent', which an agent needs to call it safely and predictably.

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. It explains 'seconds' via 'last N seconds of notes', but 'silent' is never described despite being a parameter with a default. The description covers half the parameters but leaves the other half to inference from its name.

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 uses a specific verb ('Dump') and resource ('last N seconds of notes the USER PLAYED even without recording') with a clear destination: the selected pattern. The quoted phrase 'turn what I just jammed into a pattern' reinforces intent and distinguishes it from other pattern/writing tools.

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 an explicit prerequisite: 'Select/create the target pattern first.' This tells the agent the required prior state. It does not explicitly name alternative tools or when not to use it, but the context of capturing user-played notes is clear.

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