get_project_context

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

With no annotations provided, the description carries the behavioral burden. The verb 조회합니다 strongly implies a read-only operation, and the retrieved contents are named. However, it does not mention prerequisites such as needing a valid Git repository, return format, or behavior when no active feature exists.

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 sentence with no redundant clauses. The '[MCP Tool]' prefix is unnecessary noise, but the core statement is appropriately sized and readable.

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 one-parameter read-only tool, the description is functional, but because there is no output schema or annotations, it should provide more context about return shape or prerequisites. It names the contents returned but not their structure or edge-case behavior.

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%, so the description must compensate. It only adds that project_root is a '경로' (path), which is already implied by the parameter name and title. It does not clarify whether the path should be absolute or relative, or whether it must be the repository root.

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 clearly states a specific action (조회합니다/query) and a concrete resource (Git status and currently active feature for a project_root). It is easy to understand what the tool does, but it does not explicitly contrast itself with sibling tools such as get_feature_manifest or get_learning_history.

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?

There is no guidance about when to use this tool versus its siblings. The description only says what it retrieves, not when it should be preferred over the other read-oriented tools like get_evidence or get_feature_manifest, so the agent must infer the appropriate use case.

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