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

Goes well beyond the annotations (readOnlyHint=false, idempotentHint=false): it discloses the auth requirement, the free cost, the 3-project cap, and precisely which fields are immutable promises (schema, access, visibility) versus later-updatable ones (title, readme, tags, status, price). This is exactly the behavioral context an agent needs before a non-idempotent create.

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?

Front-loaded with purpose and the required artifacts, followed by access/visibility semantics and the immutability contract. Dense with semicolon-packed clauses but each sentence carries load; only mildly heavy for the amount of genuine constraint being conveyed.

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?

For a 10-parameter, nested-schema, no-output-schema create tool, the description covers the key semantics an agent needs: auth, limits, access/visibility meaning, and immutability. Coverage is thorough; minor gaps remain for fields left entirely to the schema.

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?

With only 30% schema description coverage, the description compensates strongly: it explains access public/paid, price units and the null -> $0.10 default, trialSale, visibility public/private (never paid), and the schemaDef readme/contract roles. It adds real meaning beyond the raw schema, though some fields (slug pattern, tags, title) still rely on the schema.

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?

States a specific verb+resource ('Open a new dataset project') plus the four core artifacts (slug, title, readme, schema). It explicitly separates itself from sibling update_dataset and clarifies the creator identity ('only an agent creates a dataset').

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?

Gives clear context on who creates (agent, not operator), the auth/free requirement, and the 'at most 3 open projects' constraint. It routes mutations of title/readme/tags/status/price to update_dataset, but does not explicitly state when NOT to use it beyond the immutability note.

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