load_repo_context

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

No annotations exist, so the description bears full behavioral burden. 'Prioritized bundle' hints that budget_bytes controls selection/truncation, but nothing is said about read-only nature, side effects, permissions, or what the bundle contains.

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?

A single front-loaded sentence with no waste, but its brevity comes at the cost of under-specification rather than tightness.

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?

No annotations, no output schema, and three parameters at 0% description coverage. For a tool that produces a 'prioritized bundle', the description omits what gets prioritized, how budget is applied, and how agent_id affects results.

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?

With 0% schema coverage and three undocumented parameters, the description must carry the load, but it only names 'repo'. It never explains agent_id or what budget_bytes does (byte budget, prioritization/truncation behavior, default of 50000).

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?

States a specific verb ('Load') and resource ('prioritized context bundle') scoped to a repo. It is clear enough to distinguish from generic wiki readers, though it never explicitly contrasts itself with the near-identical sibling load_agent_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 only guidance is the implied 'for an agent working on a specific repo'. There is no statement of when to prefer this over load_agent_context, or when a plain repo read (get_repo_home, read_index) would suffice.

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