set_repository_context

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

With no annotations, the description carries full burden. It explains caching and skipping redundant lookups, but does not detail side effects like overwriting previous context, validation of the path, or session-level persistence. Adequate but not comprehensive.

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 very concise: two sentences plus an arguments section. It front-loads the purpose and contains no fluff. Every sentence is earned.

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 tool's simplicity (1 parameter) and presence of an output schema, the description is mostly complete. It explains the effect and parameter adequately, though it could mention error conditions. Overall sufficient for an agent.

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 parameter 'working_directory' has a description in the args section ('Path to the git repository root.'), which adds meaning beyond the schema's empty type string. This compensates for the 0% schema coverage.

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 caches repository context by setting the working directory and caching discovery results, distinguishing it from siblings like clear_repository_context and discover_all_repositories. It uses a specific verb 'cache' and resource 'repository context'.

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 that the tool should be used before operations that need repo context to avoid redundant git lookups, but it does not explicitly state when not to use it or mention alternative tools. It is clear enough for intended use.

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