memory_source_get

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

With no annotations and no behavioral description, the agent learns nothing about side effects, return values, or operational context. The description adds zero transparency beyond the tool name.

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 short but this is under-specification rather than effective conciseness. There is no content that earns its place; it merely repeats the tool name.

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 no output schema, no annotations, and no explanatory description, the tool is incompletely specified. Even as a simple parameterless operation, the agent has no basis to infer what 'memory source get' returns or when 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?

The tool has zero parameters, so the input schema is empty and complete. The baseline of 4 applies because there is nothing ambiguous to clarify; a higher score is not justified since the description does not proactively confirm that there are no required inputs.

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 'memory source get' is a verbatim restatement of the tool name, offering no additional meaning. It does not specify what resource is fetched, what a 'memory source' is, or how this tool differs from siblings like memory_search.

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 guidance is provided on when to use this tool versus alternatives. There is no mention of use cases, exclusions, or relationships to sibling tools.

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