memoryos_get_edtech_profile

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

No annotations are provided, so the description carries the full responsibility for behavioral disclosure. It does not state whether the tool is read-only, what happens if the EdTech schema is not enabled, whether authentication is needed, or what the response looks like. 'Fetch' implies a read operation, but the behavioral caveats are thin.

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. It states the operation, target, and condition efficiently, and every phrase earns its place.

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 simple single-parameter getter, the description provides the essential purpose and a key precondition. However, with no annotations and no output schema, it leaves open important details like behavior when the schema is disabled and the shape or content of the returned profile.

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 does not elaborate on the external_user_id parameter beyond 'for a user.' It fails to compensate for the low schema coverage by not explaining the expected ID format, where to obtain it, or any constraints around it.

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 ('Fetch') with a clear resource ('the structured EdTech profile') and target ('a user'), plus a condition ('when the EdTech schema is enabled'). This clearly distinguishes it from sibling tools like get_user_stats or get_context, which target different data.

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 a clear usage condition: use when the EdTech schema is enabled. It does not explicitly state when not to use the tool or name an alternative for non-EdTech contexts, but the condition is enough to guide an agent toward correct invocation.

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