aiworkhub_manager_context_graph_rebuild

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

With no annotations, the description must carry the full behavioral burden. It usefully discloses that this is a write operation that rebuilds derived state from an immutable ledger, but it omits permissions, idempotency, destructiveness, concurrency behavior, and whether existing derived state is replaced.

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 front-loaded sentence with no wasted words. The 'MANAGER WRITE' prefix immediately signals the operation class before the specific action.

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?

For a zero-parameter write tool with an output schema, the description covers the core action but leaves gaps around invocation safety, permissions, and expected side effects. Given the absence of annotations, it is minimally adequate rather than 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?

The tool takes zero parameters, so there is no parameter semantics to document. The schema is necessarily complete, and the description adds no parameter information because none is needed.

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 names a specific verb ('rebuild') and resource ('derived graph state') and clarifies its relationship to the immutable ledger. It is distinguishable from read-oriented context-graph siblings, but does not explicitly name an alternative tool or condition to differentiate further.

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, prerequisites, or alternatives are provided. The 'MANAGER WRITE' prefix implies a manager context, but an agent gets no rule for choosing this over related context-graph or reconcile tools.

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