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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the safety profile is fully covered by structured data. The description adds that the latestPosts include is 'bounded' and frames the tool as a read-back step before mutation, which is useful context, but it discloses nothing about permissions, rate limits, or return shape beyond what annotations and the output schema convey.

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 tightly written sentences with no filler: the capability summary leads and the operational guidance follows. Every clause earns its place and nothing is repeated from structured fields.

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 annotations covering safety, an output schema covering returns, and the schema documenting most parameters, the description supplies the remaining operational context (read-before-mutate guidance, bounded include). It is essentially complete for a no-required-param read tool, though it could say more about how filters combine.

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 description coverage is 60%, with ids, limit, cursor, and workspaceId all documented in-schema. The description only names the parameter families ('ids, filters, pagination, and a bounded latestPosts include') without adding syntax, defaults, or constraints beyond the schema. Baseline 3 is appropriate when the schema carries most of the semantic load.

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 ('Get competitor watches') and distinguishes itself from the sibling watch readers (company employee watches, signal watches) by naming the exact resource. It also enumerates the supported capabilities (ids, filters, pagination, bounded latestPosts include), so an agent can tell what the call can do without opening the schema.

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 a concrete when-to-use: 'Use this before changing a watch so the named target and current state can be read back,' which establishes the read-before-write pattern linking it to edit_competitor_watch. It stops short of naming the write sibling explicitly or stating when not to use it, so it is clear context without full exclusions.

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