myob_business_set_default

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

With no annotations provided, the description carries the full burden of behavioral transparency. It discloses that the tool sets a default, implying a state change, but does not mention side effects, permissions required, reversibility, or whether the business_id must belong to an authorized business. This is a significant gap for a mutation-like tool.

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 a single sentence with 13 words, front-loaded with the action, and contains no fluff. Every word earns its place, making it highly concise and well-structured.

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 absence of annotations and output schema, the description is too thin. It does not explain what happens on success (e.g., confirmation, return value), prerequisites (e.g., having an authorized business), or whether the default persists across sessions. A simple one-line description is insufficient for a state-changing operation.

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 one required parameter, business_id, with no description, and the tool description does not explain it beyond the term 'business/company file'. The description adds minimal meaning over the parameter name, leaving the agent to infer the identifier's format or origin. With 0% schema coverage, the description should compensate but does not.

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's purpose: setting the default MYOB business/company file for future tool calls. It uses a specific verb and resource, but does not explicitly distinguish it from sibling tools like myob_business_list_authorized or myob_company_get_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 phrase 'for future tool calls' provides clear context about when to use this tool—before subsequent operations that require a business context. However, it does not mention alternative tools or exclusions, such as when not to use it or whether the business must already be authorized.

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