inspect_project_memory

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

With no annotations, the description carries the full burden. It discloses the 'read-only' nature and the preparation of an onboarding proposal, which is helpful. However, it does not explain side effects, parameter-driven behavior, or output details beyond that proposal, leaving significant gaps.

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 succinct and front-loads the main verb, but the 'or' clause is structurally awkward and the extreme brevity omits necessary context. It is not overly verbose but under-specifies, making it less useful than a more balanced length.

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 tool with 3 parameters, no annotations, and no output schema, the description is too minimal to provide complete guidance. It does not cover parameter semantics, return values, or when to use vs. alternatives, leaving the agent to guess. The context of many sibling tools further increases the need for more detail.

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 does not explain any of the three parameters (target_root, max_depth, current_root). The agent must infer their meaning from titles alone, which is insufficient for correct invocation.

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 uses a specific verb ('Read') and resource ('target-project memory'), making the primary purpose clear. However, the disjunctive 'or prepare a read-only onboarding proposal' introduces ambiguity about whether it performs two distinct actions, and it only partially distinguishes from the sibling write_project_memory by noting 'read-only'.

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 implies use for read-only inspection and onboarding but does not explicitly state when to prefer this tool over siblings such as write_project_memory or other inspection tools. No exclusions are provided, making the usage context somewhat vague.

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