ambari_alerts_gettargets

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

The description says 'Returns all alert targets', but the input schema includes a 'page_size' parameter with default 10, implying pagination. Since no annotations exist, the description should clarify pagination behavior. It fails to disclose this important trait.

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 very concise (one sentence) but omits critical details like pagination. While not verbose, it sacrifices completeness for brevity, earning a mid-range score.

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 three parameters, no output schema, and no annotations, the description is insufficient. It does not explain the return format, pagination, or filtering capabilities, leaving the agent without essential context for correct invocation.

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 3. The description does not add any additional meaning beyond the schema's parameter descriptions, such as clarifying the 'fields' filter or 'sortBy' usage.

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 verb 'Returns' and the resource 'all alert targets', making the purpose unambiguous. However, it lacks specificity about scope or filtering, unlike the calibration example which includes date-range details.

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?

No guidance is provided on when to use this tool versus sibling tools such as 'ambari_alerts_getalerts' or 'ambari_alerts_getalertdefinitions'. There is no mention of context or alternatives.

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