indicators

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

With no annotations, the description carries the full burden. It only says 'query indicators' and lists variables, without explaining response format, pagination behavior, or potential side effects (though it appears read-only). The example does reveal some filtering fields, but not the overall behavior or output structure.

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 concise, consisting of a single sentence and an example. It is slightly front-loaded with the name and verb. The example is long but provides necessary detail about the filter structure. Overall, it earns its place without excessive verbosity.

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?

The tool has 5 parameters, no output schema, and no annotations, so the description must compensate. The example aids understanding of the query parameters, but the description does not state what the tool returns or when to use it. It is adequate for a basic query tool but leaves clear gaps.

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?

The schema covers all parameters but with shallow descriptions like 'GraphQL: String'. The description provides a rich example that illustrates the nested structure of 'filter' (feedNames, lastSeenAt, names, severity, type) and 'order' (direction, orderBy), adding meaning beyond the schema's simple type annotations.

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 states 'query indicators', which is a clear verb-resource relationship. The example variables provide concrete detail on the query capabilities. However, it does not explicitly distinguish from the sibling tool 'indicator' (singular), leaving some ambiguity about whether this is a list or single-item operation.

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 alternatives. The description only shows a query example with variables but does not mention when this tool is appropriate, what it returns, or when to prefer the singular 'indicator' tool. There are no exclusions or alternative recommendations.

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