memoryos_get_context

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

No annotations are provided, so the description carries the behavioral transparency burden. It does add one useful behavioral trait: domain schema context is included by the MemoryOS backend when enabled. 'Retrieve' implies a read operation, but the description omits other behavioral details like pagination, empty-result behavior, authentication requirements, or output format specifics.

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?

Two sentences with no filler, and the core purpose is front-loaded. The second sentence adds a relevant backend behavior detail. It is concise, though arguably too terse for a tool with 9 parameters.

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 9 parameters, no annotations, and no output schema, this description is insufficient. It does not describe return values, parameter semantics, filtering behavior, or how this tool relates to sibling context/memory tools, leaving significant gaps for an agent deciding how to invoke it.

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%, and the description explains none of the 9 parameters. The agent cannot infer the meaning or valid values for query, external_user_id, format, limit, categories, as_of, time_filter_days, context_max_tokens, or agent_id from either the schema or the description.

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?

States a specific verb ('Retrieve') and object ('prompt-ready memory context') for a tenant-scoped user, which helps distinguish it from memoryos_universal_get_context. However, it does not explicitly name any sibling or define what 'prompt-ready' means, so it is clear but not fully differentiating.

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?

No explicit guidance on when to use this tool versus alternatives such as memoryos_universal_get_context or memoryos_get_memory. 'Tenant-scoped' hints at the intended scope, but there are no exclusions, conditions, or alternative recommendations.

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