mcquest_project_context

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

With no annotations, the description carries the behavioral transparency burden. It clearly states READ ONLY and disclaims exhaustiveness with 'compact high-level understanding', which signals the tool is not a deep-dive and sets expectations about scope. No contradictions or hidden side effects are present.

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 two sentences with the READ ONLY safety signal front-loaded, followed by a concise list of what the tool returns and a clear usage recommendation. Every sentence adds value and there is no padding.

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 zero-parameter tool with an output schema, nothing critical is missing. The description states the purpose, the scope of information returned, and the best time to use it, making it complete in context.

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?

The tool has zero parameters and schema description coverage is 100%, so there is no parameter ambiguity. The description adds the semantic context that the tool is a high-level overview rather than a detailed investigation, which is appropriate for a parameterless interface.

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 the tool's function: providing a compact high-level understanding of the MCQuest project, including technology stack, directories, and key files. This is distinct from file listing or search tools, though it does not explicitly differentiate from the similarly named mcquest_project_info sibling.

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 explicitly recommends using this tool as the first context call before a large investigation, which gives concrete usage timing. It does not list exclusions or compare against alternative siblings, but the guidance is sufficient for a zero-parameter contextual tool.

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