project_context

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 discloses the return content and the 'no git subprocess' efficiency detail, but it does not explicitly state that the operation is read-only or mention any side effects, permissions, or caveats. This is a moderate disclosure.

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?

The description is a single front-loaded sentence that packs the purpose, key components, and a differentiating feature ('no git subprocess') without waste. Excellent structure and economy.

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 an output schema, the description appropriately enumerates the return items (branch, commits, handoff, memories). It maps well to the parameters and provides enough context for a simple aggregation tool, though a bit more detail on ordering or format would be nicer.

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% and both parameters ('commits', 'memories') have clear descriptions and defaults in the schema. The tool description adds no additional parameter semantics beyond that, so the baseline of 3 applies.

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 is specific and action-oriented: 'Orient in THIS project fast' followed by a clear list of what it returns (branch, commits, handoff, memories). It differentiates from sibling tools by emphasizing 'one call, no git subprocess', which is unique among memory/handoff 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?

The description clearly implies the use case: quick project orientation without invoking git subprocesses. However, it does not explicitly name alternative tools or state when not to use this one, so it's clear context but lacks formal exclusions.

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