FREE: rank compute backends by carbon for this workload — the greenest eligible path and the gCO2e saved per call. Carbon only (GR6); pair with /neurogenesis/mcp route_task for quality-floor routing.
| Name | Required | Description | Default |
|---|---|---|---|
| workload | Yes | ||
| allowed_backends | No |
| Name | Required | Description | Default |
|---|---|---|---|
| result | Yes |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations provided, the description mentions it is 'FREE' and 'Carbon only (GR6)', indicating cost and scope, but does not disclose other behavioral traits such as rate limits, mutability, or error handling.
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 two sentences long, immediately states the core purpose, and provides additional context without redundancy. Every sentence adds value.
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 complexity (nested object, output schema), the description is minimal. It explains the output (gCO2e saved) but does not elaborate on the workload input structure, which is critical for correct invocation.
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 coverage is 0%, yet the description provides no guidance on the structure of the 'workload' object or the purpose of 'allowed_backends'. The parameter semantics are mostly left to the schema, which lacks 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 clearly states the tool ranks compute backends by carbon for a given workload, identifies the greenest path, and reports gCO2e saved. It distinguishes itself from sibling tools like 'certify' and 'describe_agent' by focusing on carbon-aware routing.
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 specifies it is carbon-only (GR6) and suggests pairing with 'route_task' for quality-floor routing, providing context on when to use this tool versus alternatives. However, it does not explicitly state when not to use it.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Each tool has a clearly distinct purpose: quote_footprint computes footprint, green_route ranks backends, certify produces certificates, list_green_certificates lists them, verify_green_certificate verifies them, and describe_agent describes the agent. No overlap.
Most tools follow a verb_noun pattern (describe_agent, list_green_certificates, quote_footprint, verify_green_certificate), but 'certify' is a single verb and 'green_route' is a noun phrase, causing minor inconsistency.
With 6 tools covering footprint calculation, routing, certification, listing, and verification, the count is well-scoped for a carbon-aware routing service. No tool feels redundant or missing.
The tool set covers the full workflow: estimate footprint (quote_footprint), choose green backend (green_route), certify offsets (certify), list certificates (list_green_certificates), and verify certificates (verify_green_certificate). The describe_agent tool adds metadata. No obvious gaps.