myob_oauth_refresh

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

No annotations are provided, so the description carries the full burden. It indicates the token is 'stored' (implying state mutation) but does not disclose side effects like invalidating old tokens, network calls, authorization requirements, or failure outcomes. For a state-changing OAuth operation, this is a significant gap.

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 of 13 words, front-loaded with the action ('Refresh') and including essential scope. Every word contributes value, with no redundancy or filler.

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?

The tool is simple with one optional parameter and no annotations or output schema. The description covers the core action and business scoping, but omits return behavior and preconditions (e.g., existing authorization token). This makes it adequate for basic invocation but not fully self-contained.

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?

Schema description coverage is 0%, so the description compensates by explaining that business_id optionally targets 'one business or the default business'. This gives meaningful semantics to the parameter beyond the bare schema, though it doesn't specify the ID format or accepted values.

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 the verb 'refresh' with a specific resource 'stored MYOB OAuth access token' and scopes it to 'one business or the default business', clearly distinguishing it from sibling tools like myob_oauth_authorize or myob_oauth_logout. This is a specific verb+resource+scope structure.

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 implies usage for refreshing tokens as part of an OAuth flow but does not explicitly state when to use this tool vs alternatives, nor does it mention prerequisites or exclusions. It belongs to a lifecycle but this is not articulated, so usage is implied rather than explicitly guided.

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