get_positioning_history

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

Declares read-only operation and describes pagination with hasMore flag, but lacks details on rate limits, authentication, error handling, or empty results. Without annotations, more behavioral context would be beneficial.

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?

Three sentences, each serving a distinct purpose: purpose and output, usage context with sibling link, and behavioral note. No wasted words.

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 no output schema, describes return format (paginated JSON array with hasMore flag) and links to detail tool. Lacks field details in the array but sufficient for a paginated list tool with a sibling for detail.

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 100%, so baseline 3. Description does not add extra meaning beyond schema descriptions for projectId, page, and limit. No parameter-specific usage tips.

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?

Clearly states it retrieves paginated history of Positioning monitoring runs with completion timestamps. Distinguishes from siblings like get_positioning_run_detail and get_positioning_dashboard.

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?

Explicitly says to use it to track competitor homepage changes over time and directs to use get_positioning_run_detail for specific run data, providing clear when-to-use and alternative.

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