get_account_performance

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

Annotations declare readOnlyHint=true, and the description adds the behavioral note that an ID is not required (presumably using the session account). This is useful context beyond the annotation, but it is minimal and does not provide deeper behavioral details like response format or side effects. No contradiction with 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 concise, front-loaded with the core purpose, and the endpoint provides a useful reference. It is appropriately sized, though it could include a brief usage note without becoming bloated.

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?

With 8 optional parameters, an output schema, and similar sibling tools, the description is sparse. The structured schema and output schema carry much of the burden, but the description fails to clarify how this tool differs from get_performance_report or when to choose account-level performance over campaign/adgroup levels. It is minimally viable but has clear gaps.

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 baseline is already met. The description's 'ID 불필요' is redundant with the schema's ad_account_id description, which already states the session fallback. No additional parameter meaning is added.

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 provides an ad account performance report and includes the endpoint (GET /adAccounts/report). It uses a specific verb+resource combination. However, it does not explicitly differentiate itself from sibling report tools like get_performance_report or get_campaign_performance, which limits full clarity.

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 offers no explicit guidance on when to use this tool versus alternatives. The note 'ID 불필요' (ID not needed) hints that the tool can operate with the session account, but it does not explain selection criteria among the many sibling performance report tools.

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