unity_get_project_context

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

No annotations provided, so description carries the burden. Describes reading operation ('Get project-specific context...') with no destructive implications. However, does not detail behavior like file structure, error handling, or performance (e.g., loading large amounts of text). Adequate but could be richer.

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?

Three sentences, front-loaded with purpose, then details, then action advice. No wasted words. Highly efficient.

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?

Given simple read operation with no output schema, description is complete: explains what it does, where data lives, how to call, and when to call. No missing information.

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 already describes both parameters (category optional, port for parallel safety). Description adds value by explaining purpose ('project guidelines, architecture docs...') and contextual importance of port ('Get this from unity_select_instance').

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?

Clearly states the tool retrieves project context/documentation from Assets/MCP/Context/. Distinguishes itself by being the dedicated tool for accessing team-prepared AI agent knowledge, unlike sibling tools that are more technical (e.g., unity_project_info, unity_gameobject_info).

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?

Explicitly advises to call early in the session and to omit arguments for all context or specify a category. The 'IMPORTANT' emphasis provides clear when-to-use guidance.

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