Changed Symbols

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

Annotations already indicate readOnlyHint=true and destructiveHint=false, so the safety profile is clear. The description adds that it returns 'symbols changed since last scan/watch', which provides context about the data scope but omits details like pagination, ordering, or behavior when no changes exist.

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?

Description is a single, short sentence that directly states the purpose. While concise, it could benefit from a second sentence for parameter clarification without losing brevity.

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?

Given two parameters, no output schema, and multiple sibling tools, the description is incomplete. It does not explain the limit parameter's effect, the return format, or how to handle cases where no scan/watch has occurred.

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 0%, so the description must explain parameters. However, it does not mention limit or repository_id, leaving their purposes unclear. No additional meaning beyond the schema's type and default is provided.

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?

Description states 'Symbols changed since last scan/watch for a repository' which clearly conveys the tool's function and resource. It distinguishes from sibling tools like project.scan or project.watch_start by focusing on retrieving changes rather than initiating scans or watches.

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?

No explicit guidance on when to use this tool vs. alternatives. The description implies usage after a scan or watch, but does not specify prerequisites or mention when to use other tools like symbol.source or project.snapshot.

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