ad_manager_google_get_entity

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

Beyond annotations (which already declare read-only, idempotent, non-destructive), the description adds no behavioral insight. It does not state whether it returns a single entity or a list, how IDs interact, or any other operational details. The description carries the burden for these traits but provides nothing.

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?

While concise, it is drastically under-specified. A two-word phrase is not a useful description for a tool with nine parameters and multiple enums; it fails to convey any structure or essential information.

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 9 parameters and no output schema, the description is completely inadequate. An agent cannot infer purpose, usage, or expected behavior from this terse text, making the tool nearly unusable without external knowledge.

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 each parameter already has a description. The tool description adds no additional meaning, but the baseline of 3 is appropriate since the schema is sufficient.

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?

Description 'Get entities' is essentially a tautology of the tool name, providing no specificity about what entities (campaigns, ad groups, ads) or from which platform. It fails to distinguish from many sibling get tools like ad_manager_google_get_campaign_by_id or ad_manager_fb_get_entity.

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 zero guidance on when to use this tool instead of its many alternatives. No mention of use cases, required parameters, or exclusions.

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