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

No annotations are provided, so the description carries the full burden for this mutation tool. It discloses the ownership requirement, but says nothing about side effects, idempotency, whether it overwrites an existing finding of the same title, or what the operation returns on success. It also introduces a subtle ambiguity about how the 'sql' parameter relates to a 'q' that looks like SQL.

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?

The purpose is correctly front-loaded, but the query-language syntax is delivered as one very long, unformatted sentence that is hard to scan. The content is high-value, yet a bulleted or clause-separated structure would carry the same information more efficiently.

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 ten-parameter mutation tool with no annotations and no output schema, the description is rich on filter syntax but thin on operation semantics. It leaves the agent unsure of the write's effect and return behavior, though the 100%-covered schema compensates for the parameter side.

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 already 100%, which sets a baseline of 3, but the description adds substantial meaning beyond the terse schema descriptions: full query-language grammar for 'q' (ranges, ISO dates, dot paths, tags, OR/parentheses), SQL fallback against table `data`, and the comma/`-` syntax for 'sort' and 'cols'. It omits any commentary on note, token, version, or row_count, so it stops short of a 5.

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?

The description states a specific verb and resource ('Pin a finding') and helpfully defines the term with the parenthetical '(a saved, titled view)'. That definition is the main thing preventing confusion with siblings like push. It does not, however, differentiate itself from those siblings or explain how a finding relates to a dataset push.

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?

The only usage context offered is the ownership constraint ('a dataset you own'), which functions as a prerequisite. There is no guidance on when to pin a finding versus using the sibling 'push', no exclusion conditions, and no note on whether re-pinning an existing title is expected.

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