create_resource

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

No annotations provided, so description carries full burden. Only states 'Create a resource' implying mutation. No disclosure of authorization, idempotency, error behavior, or side effects. Mentions external_id usage in evaluation calls but lacks deeper behavioral transparency.

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 concise sentences: first defines purpose, second adds critical usage guidance. No wasted words.

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 core purpose and primary parameter guidance. Lacks description of return value (no output schema) but is adequate for a simple create operation. Could mention typical success/error responses, but overall sufficient.

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% (baseline 3). Description adds significant value for external_id by explaining its purpose and benefit. For other parameters, little beyond schema, but the added detail on external_id raises the score.

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?

Clearly identifies the verb 'Create' and the resource 'resource' (a specific instance of a resource type). Examples given (document, project) and distinguishes from sibling tools like create_resource_type by specifying 'instance of a resource type'.

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 guidance to use this tool for creating specific resource instances. Recommends setting external_id for evaluation-time referencing. Missing exclusions or comparisons to other creation tools, but context from sibling names partially compensates.

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