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

With no annotations, the description provides minimal behavioral context. It does not disclose whether the tool is read-only, returns immediate results or initiates a job, or any side effects. The phrase 'track local visibility' implies ongoing monitoring but no behavioral specifics.

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 description is very concise (one sentence) and front-loaded. However, it sacrifices essential information, making it insufficient for an agent to fully understand the tool's behavior. It is appropriately sized but lacks clarity.

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 the tool has 5 parameters, no output schema, and numerous similar siblings, the description is incomplete. It does not explain return values, the effect of optional parameters like 'sync' or 'language', or constraints like keyword/location limits. An agent would need additional information to use it effectively.

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 low (20%), with only the 'domain' parameter described. The description adds no clarification about the meaning of 'keywords', 'locations', 'sync', or 'language'. It vaguely mentions 'across keywords and locations' but does not compensate for the schema gaps.

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 clearly states the tool's action ('track local visibility') and the resources involved ('domain', 'keywords', 'locations'). It distinguishes from siblings like agentseo_rank_track by specifying 'local visibility' and 'across keywords and locations', but does not explicitly differentiate from closely related tools like agentseo_local_audit.

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 guidance is provided regarding when to use this tool versus its siblings, nor any exclusions or prerequisites. The description lacks context on the appropriate scenarios for local visibility tracking vs. other local SEO analyses.

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