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

With no annotations, the description has to carry behavioral weight; 'Fetch' and 'active' do convey a read-only operation scoped to the current statement rather than history. However, it says nothing about permissions, whether historical/superseded statements are addressable, or any other operational constraint.

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?

One short, front-loaded sentence with the action first and the discriminating detail ('active') before the kind list. No filler or redundant clauses.

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 the single required enum parameter is fully covered. The only remaining gap is the absence of routing guidance against the many sibling memory readers, which is a minor omission for such a simple getter.

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% and the single enum parameter is fully documented, so the schema does the heavy lifting. The description only restates the three enum values ('vision, mission, or purpose') without adding format or selection semantics beyond the schema.

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 ('Fetch') and resource ('the active org statement') with the three allowed kinds named inline. It is clearly distinguishable from its sibling memory_strategic_statement_set, though it does not name other related readers like memory_strategic_plan_get.

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 word 'active' hints that only the current statement is returned, but there is no explicit guidance on when to call this versus memory_strategic_plan_get, memory_soul_get, or other strategic readers. No prerequisites or exclusions are stated.

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