get_context

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

No annotations are provided, so the description must carry behavioral disclosure. It does disclose that passing project_path activates the IDE workspace as default, a side-effectful behavior, and uses 'Read' to signal a non-mutating operation. It does not explain refresh/format defaults or whether any re-indexing occurs, but it avoids contradiction.

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?

Two sentences: the first states purpose with specific content, the second gives a concise setup instruction. No redundant filler.

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?

The description gives a solid purpose and one parameter's behavior, but without annotations or output schema it leaves gaps: it does not describe the output format/length or how refresh/limit alter results, and it lacks guidance relative to sibling tools. It is adequate but not comprehensive.

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 0%, and the description only adds semantics for project_path ('activate the current IDE workspace as the default'). It does not explain the meaning or effect of limit, format, or refresh, leaving the agent to infer from the schema alone.

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 specifies a clear action ('Read') and a concrete resource ('balanced YAML context layer') with listed contents (repo overview, Git state, task, memory, AST-first handoff guidance). It is not a tautology and conveys a distinct purpose, though it does not explicitly contrast with sibling tools like project_memory.

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?

It clearly implies when to use it — when you need repo overview, Git state, task, memory, or handoff guidance — and includes a practical activation instruction ('Pass project_path once...'). However, it does not provide explicit exclusions or alternative tool recommendations, so it stops short of the strongest guidance.

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