ghg-ledger__classify_activity

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

With no annotations, description must disclose behavioral traits. It does so by stating 'deterministic', 'No inference is used', and 'unknown activity types return no suggestion', giving clear expectations about operation and edge cases.

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?

Two sentences succinctly convey purpose and critical behavioral details. No wasted words; front-loaded with the most important information.

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?

Despite clear purpose, the tool lacks output schema and does not describe return format. The parameter structure is opaque. For a classification tool, more details on input format and output expected are needed for complete understanding.

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?

Input schema has one required 'activity' parameter (object with additionalProperties) and 0% description coverage. The description does not explain the expected structure or properties of the activity object, leaving the agent uncertain about how 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?

Description clearly states verb 'Suggest' and resource 'scope and Scope 3 category', and distinguishes from sibling 'ghg-ledger__calculate_inventory' by focusing on classification from a bundled deterministic map.

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?

Implies use for classification before inventory calculation, but does not explicitly state when to use this tool vs alternatives like calculate_inventory or get_factor_pack. No exclusions or when-not-to-use guidance.

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