abn_lookup

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

No annotations are present, so the description carries full burden for behavioral disclosure. It does not mention read-only nature, authentication requirements, rate limits, or return format. The minimal description fails to inform agent behavior beyond the basic action.

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?

While the description is short (one sentence), it is under-specified rather than concise. It lacks structure and fails to deliver necessary information. For a tool with two parameters and no annotations, a more structured description is expected.

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 low schema coverage, no output schema, and no annotations, the description is highly incomplete. It does not explain what data the lookup returns, leaving the agent without sufficient context to use the tool effectively.

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%, and the description adds no meaning to the parameters 'abn' and 'api_key'. It does not clarify the expected format for 'abn' or the purpose of 'api_key'. This is a critical gap for a 2-parameter tool.

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 'Look up an Australian Business Number (ABN),' which is a specific verb and resource. It clearly indicates the tool retrieves details for a single ABN, distinguishing it from the sibling 'abn_search' which likely searches multiple ABNs. However, no explicit differentiation is provided.

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 guidance on when to use this tool versus alternatives like abn_search, nor does it mention prerequisites or contexts. The agent receives no decision support.

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