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

While annotations confirm it is read-only, the description adds valuable operational constraints: the data is limited to 'metadata/approved fields only.' This informs the agent about the scope and fidelity of the returned data, preventing misuse.

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 highly concise and front-loaded. Both sentences are efficient, with the second sentence specifically detailing data safety/scope constraints without being overly verbose.

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?

Despite having three functional parameters, the description is incomplete. It tells the agent what data is *safe* to receive (no secrets), but provides zero functional context on how to actually *ask* for the data using the available input parameters.

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%. The description does not add any meaning to the parameters like 'query', 'limit', or 'offset,' nor does it specify how those parameters should be used to filter or paginate the data. It is entirely useless for guiding parameter invocation.

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 reads location compliance analytics. However, it is generic and fails to distinguish this specific function from similar siblings like 'get_site_compliance_analytics' or 'get_location_compliance_summary,' leading to potential ambiguity.

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?

There is no guidance provided on when to use this tool over others in the compliance/analytics domain. It doesn't explain what conditions trigger the need for this tool.

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