get_business_context

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

With no annotations, the description carries the burden of disclosing behavior. It does state the return format (markdown-formatted), which is useful, but it omits edge-case behavior such as what happens if no context has been set yet, and it does not explicitly confirm that the operation is read-only.

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 short and front-loaded. The first sentence states the purpose, followed by a brief explanation and a clear Args/Returns structure. No redundant sentences.

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?

For a zero-parameter getter, the description covers the essential return format and data source. It lacks a note about prerequisites (e.g., needing to set the context first), but given the simple nature and presence of sibling tools, this is a minor gap.

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 input schema has zero parameters, so the baseline is 4. The description does not add user-facing parameter semantics, but it mentions an internal 'ctx' parameter for logging, which is extra context beyond the schema, though potentially confusing if considered a user input.

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 states a specific verb ('returns') and resource ('business context'), and clarifies the origin ('created from the answers to the clarification questions'). This distinguishes it from siblings like set_business_context or get_business_context_features.

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 clearly implies this is the retrieval counterpart to set_business_context, with context about the source of the data. However, it does not explicitly state when not to use it or mention alternatives like get_business_context_features, leaving some room for ambiguity.

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