save_writeup

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

No annotations are provided, so the description must convey behavioral traits. It only says 'Save,' implying a write operation, but does not disclose whether it overwrites existing entries, requires specific permissions, or has any side effects. The description lacks detail on consequences or limits.

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 two sentences, concise and to the point. It first states the action and example, then states the purpose. No unnecessary words, but it could be slightly more structured by defining each parameter.

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 simple schema (3 required string parameters) and no annotations, the description provides minimum viable completeness. It explains the overall purpose and usage but leaves gaps in parameter roles and output behavior. The existence of an output schema (not shown) might compensate, but the description alone is incomplete.

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?

With 0% schema description coverage, the description should compensate, but it only adds minimal context. The parameters agent_id, title, and writeup are not explained beyond the example. The description mentions 'writeup' and 'action' but does not clarify the role of agent_id or title semantics.

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 clearly states the function: 'Save a short writeup or explanation of an action' with a concrete example ('how you elevated privileges'). It distinguishes the tool from siblings like log_finding by specifying it's for recording successful techniques for later review, but does not explicitly differentiate it from similar 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 provides context on when to use the tool: after an action to record a technique. It says 'Use this to record successful techniques for later review,' which implies usage but does not specify when not to use or mention alternatives like log_finding.

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