myob_approval_get

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

With no annotations, the description carries full responsibility for behavioral disclosure. 'Get' and 'preview' imply a read-only operation, but the description does not explicitly state that this call does not modify or consume the approval, nor does it mention authentication requirements, error behavior, or what 'full preview' entails.

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, front-loaded sentence with no unnecessary words. It efficiently conveys the core purpose.

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 lack of annotations and output schema, the description is too terse. It does not explain what a 'full approval preview' contains, how it integrates with the approval workflow (list/approve/deny), or any preconditions (e.g., the operation must exist). An agent would need additional context to confidently invoke this tool.

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 0% description coverage and one required parameter, operation_id. The description adds that it is for 'a MYOB operation', providing minimal context, but does not explain what an operation is, where to obtain the ID, or its format. It only partially compensates for the lack of schema descriptions.

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 'Get the full approval preview for a MYOB operation' uses a specific verb ('Get') and resource ('full approval preview') with a scope ('for a MYOB operation'), clearly distinguishing it from siblings like myob_approval_list_pending (lists), myob_approval_approve/deny (mutations).

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 provides no explicit guidance on when to use this tool versus alternatives. Usage is implied by the name and sibling context (list pending → get preview → approve/deny), but not stated in the description.

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