adsense_get_account

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

With no annotations provided, the description carries the full burden of disclosing side effects. It only says 'get', implying a read-only operation, but does not explicitly confirm it is non-destructive, nor does it mention permission requirements, error behavior, or return value characteristics. The minimal disclosure is insufficient for safe invocation.

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 with an example, containing no filler. Every word adds value and it is front-loaded with the core action.

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 the tool's low complexity (one parameter, no output schema), the description covers the basics but omits details like return value structure, error handling (e.g., what happens if account doesn't exist), and any authentication or permission notes. Since there is no output schema, explaining what is returned 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 0%, so the description must compensate. It indirectly explains the 'account' parameter by saying 'by resource name' and gives an example format ('accounts/pub-123'), which clarifies the required pattern. However, it does not explicitly name the parameter or explain its full semantics (e.g., must start with 'accounts/'), leaving some ambiguity.

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 action: 'Get one AdSense account by resource name' with a specific example. It distinguishes from siblings (adsense_list_accounts for multiple, adsense_generate_report for reporting) by focusing on retrieving a single account by its resource identifier.

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?

Usage is implied through the phrase 'by resource name' and the example, but there is no explicit guidance on when to use this tool versus alternatives like list_accounts. It does not state when not to use it or mention prerequisites (e.g., need a known account resource name).

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