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

No annotations are supplied, so the description carries the full disclosure burden. 'Fetch' implies a read, but it does not state read-only semantics, behavior when the id is not found, or any permission requirement, leaving the behavioral profile essentially undocumented.

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?

A single short sentence with the key constraint ('one', 'by type and id') front-loaded and no wasted words. It is efficient, though its brevity is part of why the routing and behavioral gaps above exist.

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?

An output schema exists, so return values need no explanation, and both parameters are fully documented in the schema. What is missing is the disambiguation between this generic entity getter and its typed siblings, which matters given the crowded catalog.

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 100%, with entity_type fully enumerated and entity_id documented as a UUID, so the schema does the heavy lifting. The description's 'by type and id' only restates that contract without adding format or constraint detail, making the baseline 3 appropriate.

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 and resource (fetch one strategic entity) plus the lookup keys (type and id), which is clearer than a bare name restatement. However, it does not differentiate itself from the type-specific siblings memory_strategic_statement_get and memory_strategic_plan_get, which cover overlapping ground.

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 when-to-use guidance is given. With near-duplicate siblings such as memory_strategic_statement_get, memory_strategic_plan_get, memory_entity_view, and memory_get in the catalog, the agent has no stated basis for choosing this generic getter over a typed one.

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