myob_business_list_authorized

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

The description accurately describes the read-only nature via the verb 'List', but it does not disclose details like whether it requires authentication, what it returns if no businesses are authorized, or whether it has any side effects. With no annotations provided, the description carries the burden, and it only provides minimal behavioral context.

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 that is clear and front-loaded. It conveys the essential information without any filler, achieving high conciseness.

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 simplicity of the tool (no inputs, no output schema), the description is mostly complete: it names the resource and the scope. It could benefit from clarifying what the returned list contains (e.g., IDs, names) but this is not critical because the operation's purpose is obvious.

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 tool has zero parameters, so the schema coverage is 100% by default. The description doesn't need to explain any parameters, and the baseline of 4 applies. It adds no param information because there are none to add.

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 uses a specific verb 'List' with a clear resource ('MYOB businesses/company files') and a scope ('already authorised on this machine'). It distinguishes this tool from siblings like myob_company_list_files or myob_auth_status by emphasizing the authorization and local machine 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?

No guidance is given on when to use this tool versus alternatives. It does not mention situations where one would prefer this over myob_auth_status or myob_company_list_files, nor does it state any prerequisites or post-conditions. The usage context is only vaguely implied by the description.

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