zdx_get_application

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

Annotations already declare readOnlyHint=true; the description redundantly says 'Read-only.' It adds the time window constraint and return structure (headline score + per-region breakdown), but does not disclose other behaviors like response format or pagination. With annotations covering the safety aspect, the description adds moderate value.

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 extremely concise with no wasted words. Four sentences each add value: purpose, safety, return detail, parameter source. Front-loaded and efficient.

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 5 parameters, 0% schema coverage, and no output schema, the description should explain all parameters. It covers only app_id and since, leaving geo_id, location_id, and department_id unexplained. The output structure is vaguely described, which may suffice for a simple tool but lacks completeness for nuanced usage.

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 only explains two of five parameters: app_id (source) and since (time window, default 2h). Parameters geo_id, location_id, and department_id are entirely undocumented, leaving their meaning unclear. This is insufficient for effective tool use.

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 'Get the ZDX score for one application, with its most-impacted regions.' It uses a specific verb ('Get') and resource ('ZDX score'), and distinguishes from siblings like 'zdx_list_applications' by focusing on a single app's score with regional breakdown.

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 advises to 'Use `app_id` from `zdx_list_applications`,' providing a clear prerequisite. While it doesn't explicitly exclude alternatives, the context implies use when you have an app_id. No direct guidance on when not to use it, but the sibling tools are distinct.

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