business_context_list

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

No annotations are provided, so the description must disclose all behavioral aspects. It says nothing about side effects, required permissions, read-only vs. mutation, pagination, or return format. For a tool that likely performs a read operation, this is a major omission—the agent has no clue what happens when it's called.

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 extremely short, but this is not conciseness—it's under-specification. While the brevity is technically efficient, it provides no actionable information, so the structure fails to serve the tool's purpose. Nothing is front-loaded because there is no content at all.

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 9 parameters, no annotations, and no output schema, the description must supply substantial context, but it provides none. The agent lacks any understanding of input requirements, outputs, or how this tool integrates with the broader context system. This is completely insufficient for effective usage.

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 9 parameters with 0% coverage from the description. Required parameters like repository_id and target_commit are completely unexplained. No parameter names or purposes are elaborated, and the description adds zero detail to help the agent construct a correct call. With such a high parameter count, this is critically inadequate.

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 'business context list' is a near-verbatim restatement of the tool name. It fails to state what the tool actually does—what type of context it lists, what a 'business context' is, or how it differs from siblings like business_mapping_list or list_contexts. An agent cannot determine the tool's core function from this description.

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?

There is no guidance on when to use this tool versus alternatives. With numerous sibling tools such as business_mapping_list, list_domains, and list_concepts, the complete lack of usage direction leaves the agent without any basis for selection. No intended scenarios or exclusions are mentioned.

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