mcp_engram_set_geosphere_frame

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

Discloses internal behavior: synthesizes a deterministic normalized 8192D lens vector, installs it into SymplecticState register, and that it is reproducible for same inputs. No annotations provided, but description is detailed. Lacks mention of potential side effects or idempotency.

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?

Concise but comprehensive; front-loads purpose, then explains process and effect. Could be slightly more compact, but every sentence adds value.

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?

Covers purpose, inputs, internal process, effect on future queries, and return type (confirmation with frame_step). No output schema, so return info is adequate. Missing details on frame_step format, but overall complete.

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?

Adds meaning beyond schema: provides examples for origin ('giza_sacred_cubit', etc.) and time_offset ('sowing_moon', '1776-07-04'). Schema coverage is 100%, so description complements schema effectively.

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?

Clearly states the verb 'Set' and resource 'Geosphere frame (5th coordinate)'. Distinguishes from sibling tools like mcp_engram_get_geosphere_frame and mcp_engram_clear_geosphere_frame by specifying it is for setting a frame for subsequent queries.

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?

Explicitly states effect on 'all subsequent queries' and mentions that 'recall/query_with_momentum' will use this lens. Could be more explicit about when not to use or prerequisites, but provides clear context for usage.

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