ghg-ledger__classify_activity

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

It discloses deterministic behavior and handling of unknown inputs, which adds value beyond the absence of annotations. However, it does not mention whether the tool is read-only or has side effects.

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 short and front-loaded, but the first sentence is slightly opaque ('deterministic map'). It could be clearer while maintaining brevity.

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 output schema and minimal input description, the description is insufficient for the agent to use the tool correctly. It omits details on the activity object structure and return format.

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 sole parameter 'activity' is an open-ended object with no schema details in the description. Schema coverage is 0%, and the description provides no guidance on its structure, leaving the agent unable to construct valid input.

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 action ('Suggest') and the resource ('scope and Scope 3 category'), and distinguishes it from sibling tools like calculate_inventory. However, 'bundled deterministic map' is vague.

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 explains that no inference is used and unknown types return no suggestion, indicating when it applies. But it does not explicitly state when not to use it or compare with alternatives.

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