retrieve_event_tracking_status

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

Annotations already declare readOnlyHint=true and destructiveHint=false. The description reinforces 'Fetches data. Makes no changes' and adds that it gets enabled/disabled status. However, it does not elaborate on response format or additional behavior beyond what annotations cover.

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 somewhat redundant, repeating 'Retrieve Event Tracking Status' and 'Get event tracking status'. The emoji and endpoint info add minor value. Could be more concise without losing 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?

The description provides basic info for a simple status retrieval, but lacks output format details (no output schema). It suffices for the tool's simplicity, but an agent might need to infer the exact structure of the status response.

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. The description adds no additional meaning to parameters like limit, offset, orders, or filters. It does not explain how pagination or sorting applies to status retrieval.

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 it retrieves event tracking status using the verb 'Retrieve' and specific resource 'Event Tracking Status'. It distinguishes from sibling mutation tools like 'enable_disable_event_tracking' by emphasizing read-only nature, and from 'retrieve_site_tracking_status' by focusing on event tracking.

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?

The description implies usage for reading status but lacks explicit guidance on when to use this tool versus alternatives like 'enable_disable_event_tracking' or 'retrieve_site_tracking_status'. No when-not or exclusion statements are provided.

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