get_inheritable_context

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

No annotations provided. The description hints at behavior (layered package, flagged hypotheses, invitations) but doesn't disclose side effects, permissions, or return structure. It relies on vague metaphors.

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?

Three short, front-loaded sentences. Conciseness is good, but poetic language may obscure meaning. Still efficient.

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?

Without output schema or annotations, the description should clarify what the tool returns and how it fits into the workflow. It names three components but doesn't specify if they are all, filtered, or contextualized.

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?

No parameters exist, so schema coverage is 100%. Baseline for 0 params is 4; the description adds no param info, which is 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?

The description says 'Build the layered context package for the next instance,' which gives a general idea but lacks specificity. It mentions ground truth, hypotheses, and open threads, but doesn't clearly differentiate from siblings like get_compaction_context or get_open_threads.

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 guidance on when to use this tool versus alternatives. With a large sibling list, this omission makes selection harder for the agent.

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