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

Annotations cover safety (readOnlyHint=false, destructiveHint=false), but the description adds context they don't: the snapshot is permanent and the link never changes, and the tool 'Needs a token' (auth prerequisite). That is real behavioral value beyond the structured fields. It doesn't explain what happens on repeated calls or what is returned, so not a 5.

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, both earning their place: the core action and permanence first, then the when-to-use guidance. No filler or redundancy.

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 2-parameter tool with no output schema, the description conveys enough: what it creates (numbered version), that it's permanent, when to call it, and that a token is required. The one gap is that it never explains the slug parameter, which an agent must supply and whose format is undocumented.

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 50%: the 'note' parameter is documented in the schema, while 'slug' is not. The description implies the target is 'a table you run' but never says slug is the table identifier, nor does it clarify the note/version-label relationship. At 50% coverage the description should compensate more than it does, so baseline 3.

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 and resource: it freezes a table into a numbered, immutable version with a permanent link. An agent can distinguish this from fork_table or export_table because the description emphasizes a frozen snapshot as-it-stands-now rather than a live copy or export. It stops just short of naming a sibling outright, keeping it at 4 rather than 5.

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 concrete triggering conditions: 'Do this before training on a dataset or citing a table.' That tells the agent exactly when the tool is appropriate. It does not say when not to use it or name an alternative tool, so it falls short of a 5.

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