offsets__register_project

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

With no annotations, the description carries full burden for behavioral disclosure. It reveals that project_id is immutable after registration, which is useful. But it omits other key behaviors: idempotency, duplicate handling, error conditions, return value, or permissions needed. This is insufficient for a mutation tool.

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 concise (three sentences) and front-loaded: it opens with context, then the main action. Every sentence adds value without redundancy. Minor improvement could be structuring key constraints (e.g., required params) more explicitly, but it is already efficient.

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 no output schema, no parameter descriptions, and no annotations, the description is the sole source. It covers purpose and two constraints but fails to explain the effect of optional parameters, success/failure responses, or how this tool fits into the offsets workflow (e.g., after registration, use offsets__list_projects or offsets__project_funding). This incompleteness hampers correct usage.

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%, so description must compensate. It adds meaning for verification_ref (D-Score/land-verification/registry id) and project_id (immutable), but does not explain name, location, beneficiary, methodology, or registry_ref. The required parameters are partially covered, but the optional ones are left entirely to the schema (which has no descriptions), leaving semantic gaps.

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 action ('Register a VERIFIED restoration project') and the resource (project within a verified-credit carbon offset clearinghouse). It distinguishes from other offsets tools by specifying registration with verification_ref required, and notes that project_id is immutable, setting it apart from tools that list or fund projects.

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 implies usage context: only verified conservation projects should be registered (since verification_ref is required and 'only verified conservation is funded'). However, it does not explicitly state when not to use this tool or suggest alternatives like offsets__list_projects or offsets__project_funding.

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