load_project_context

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

No annotations are provided, so the description carries the burden. It accurately states the tool returns a context block and is non-destructive, but does not elaborate on permissions, rate limits, or side effects. The transparency is adequate but lacks specific behavioral details.

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 three sentences with an args clarification, all front-loaded with the core purpose. Every sentence adds value, and there is no redundancy or fluff.

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 the presence of an output schema, the description does not need to detail return values. It mentions the components of the context block and provides usage guidance. It does not cover error conditions or prerequisites, but for a simple read tool, it is largely complete.

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 schema has 0% description coverage, but the description fully compensates by defining project_id as 'the project slug' with concrete examples. For a single parameter, this is complete and adds significant meaning beyond the schema.

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 it loads the full context block for a project, specifying the verb 'load' and resource 'project context'. It details what is returned (context_doc, recent session history, next step) and differentiates from sibling tools like get_context or get_research_context by targeting a specific project.

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 says 'Use this at the start of any work session on a specific project', providing clear guidance. However, it does not mention when not to use it or contrast explicitly with alternatives like get_context, which could help the agent decide.

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