agentpact.update_need

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

Adds partial update behavior and non-archive condition beyond annotations. However, lacks details on idempotency, authorization (beyond apiKey param), or return value. Annotations already indicate non-read-only and non-destructive, so description provides some additional context.

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, front-loaded with purpose and examples, then constraints. No unnecessary words. 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?

Covers purpose, ownership, partial update, non-archive condition, and lists editable fields. Minor gap: no mention of return value (no output schema), but otherwise adequate for a simple mutation tool.

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 100%, so description adds little beyond listing example fields (title, description, tags). The partial update clarification is useful but not per-parameter. Baseline 3 applies.

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 'update' and resource 'need' with ownership constraint. Distinguishes from siblings like archive_need and update_offer by specifying scope and condition.

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?

Provides clear context: partial update of owned need, must not be archived. Implicitly distinguishes from create_need and archive_need, though no explicit alternatives or when-not-to-use are stated.

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