create_extension

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

Annotations do not provide rich behavioral hints (readOnlyHint=false, destructiveHint=false). Description adds that it returns the block ID, but does not disclose side effects, prerequisites, or limitations beyond creation.

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 with no extraneous information. Front-loaded with the key action and result.

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?

With full schema documentation and a clear purpose, the description covers the main usage. Could mention error conditions or prerequisites, but overall adequate for a creation 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?

All four parameters have descriptions in the schema, achieving 100% coverage. The description does not add additional context beyond the schema, so baseline 3 is appropriate.

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 states 'Create a new extension (block) in an Airtable base' with specific verb 'create' and resource 'extension'. Distinguishes from sibling 'install_extension' by mentioning it returns block ID needed for installation.

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?

Explicitly says 'Use this to register custom extensions before installing them', indicating the workflow order. Does not explicitly list when not to use, but context implies creation before installation.

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