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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is partly covered; the description reinforces this with 'read-only, never writes'. It adds genuinely useful behavior beyond annotations — Alia performs multi-step retrieval internally and reports grounding level — but the richest behavioral detail (answer/references/confidence semantics) is really return-value documentation, not invocation behavior.

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?

Front-loaded with purpose and the alternative-routing rule, then structured input/output blocks that scan well. Slightly over-long — the 'Input: { question, topicId? }' line largely restates the schema and could be trimmed.

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?

No output schema exists, so the description carries the full burden of explaining returns, and it does so completely: answer prose, references with id/title/type and their reuse as public_ids for other tools, and the three confidence states including the not_found honesty guarantee.

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 coverage is 100%, so the baseline is 3; the description nevertheless adds the operative meaning that topicId is only a hint Alia may range beyond and that omitting it makes the question whole-workspace, which the schema does not spell out as clearly.

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 — ask one natural-language question, get one synthesised grounded answer — and explicitly names the siblings it replaces (engramic_search, engramic_topic, engramic_timeline). An agent can tell exactly what this returns versus the granular read tools.

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?

Gives explicit when-to-use ('when you just want the answer to a question about what this workspace knows') and when-not-to-use ('reserve the granular read tools for when you need to navigate the graph yourself'), plus the topicId scoping rule (hint to focus vs omit for whole-workspace).

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