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

Annotations include readOnlyHint=true, indicating a safe read operation. The description adds valuable context by disclosing the API key requirement (pro, growth, or agency), which goes beyond the annotation. No contradiction exists between description and annotations.

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 two concise sentences, front-loaded with the action ('Return pending and completed competitor actions') and includes only necessary info (auth requirement). Every word earns its place.

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 simple single-parameter getter with readOnlyHint annotation, the description covers the core functionality and auth. It does not describe return structure, but given no output schema and low complexity, this is mostly sufficient. Minor gap: lacks any mention of rate limits or error cases.

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 compensate. It mentions 'for a domain' but adds no additional detail about format, constraints, or validation beyond the schema's 'domain' field. The single parameter is minimally elaborated.

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 returns pending and completed competitor actions for a domain, specifying the resource, scope, and type of data. The verb 'return' is specific, and the resource is distinct from sibling tools like get_quick_wins or get_bot_activity.

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 by stating it returns competitor actions for a domain. However, it does not explicitly discuss when to use this tool over alternatives or provide exclusions. The auth requirement is mentioned but not used as a differentiator.

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