configure_image_tracking

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

The tool has readOnlyHint=false (mutation) and the description says 'configures', which implies changes. However, it does not disclose side effects like whether changes reset existing tracking, require the system to be running, or are persistent. The description adds minimal behavioral context beyond the annotation.

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 a single concise sentence that front-loads the verb. It avoids unnecessary details and is easy to parse, though it could be slightly more specific about the tool's domain.

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 6-parameter configuration tool with no output schema, the description is sparse. It does not explain return behavior, error states, or whether settings are applied immediately. More context about the AR image tracking domain and configuration lifecycle would improve completeness.

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 100%, so the schema already explains each parameter. The description only provides a high-level summary without adding new meaning, thus baseline score of 3 is appropriate.

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 configures image tracking settings and lists example parameters (how many images, quality, update frequency). This distinguishes it from sibling tools like 'add_tracking_image' or 'get_tracked_images', but does not explicitly contrast with other 'configure_*' tools.

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 on when to use this tool versus alternatives, such as when to adjust tracking parameters instead of adding images. The description lacks context about prerequisites or typical use cases.

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