roampal-core

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

With no annotations provided, the description carries full burden for behavioral disclosure. While it mentions what the tool stores ('key takeaways'), it doesn't describe important behavioral aspects like whether this is a write operation, what permissions are needed, how data is persisted, or what happens on success/failure. The description adds minimal behavioral context beyond the basic purpose.

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 extremely concise with just two sentences that each earn their place. The first sentence states the core purpose, and the second provides important exclusion guidance. There's zero wasted text, and the information is front-loaded appropriately.

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 a write operation tool with no annotations, no output schema, and 0% parameter documentation in the schema, the description is incomplete. It covers basic purpose and some usage boundaries but lacks crucial information about behavioral characteristics, parameter details, and expected outcomes that would be needed for proper tool invocation.

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 for the single parameter 'key_takeaway', the description provides no additional semantic information about this parameter. It doesn't explain what constitutes a valid 'key_takeaway', its format, length constraints, or examples. The description fails to compensate for the complete lack of schema documentation.

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 tool's purpose with specific verbs ('store key takeaways') and resources ('from significant exchanges'), making it immediately understandable. However, it doesn't explicitly distinguish this tool from all sibling tools beyond just 'add_to_memory_bank'.

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 explicit guidance on when NOT to use this tool ('NOT for permanent preferences or standing rules') and names an alternative ('use add_to_memory_bank for those'), which is helpful. However, it doesn't clarify when to use this tool versus other siblings like 'update_memory' or 'search_memory'.

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