signallord_get_data_health

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

Annotations declare read-only, idempotent, non-destructive. Description adds that stale means degraded data, downstream values may be estimated/held over, and details access restrictions for operator scope (403 if not allowed). No contradictions.

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?

Two short sentences plus one explanatory sentence. Front-loaded with action and context. No fluff.

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?

Output schema is present, so return format is covered. Description covers purpose, when to use, what stale means, and access restrictions. Complete for a simple health-check tool with two optional 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 provides description for 'scope' but not 'response_format' (50% coverage). The description adds context on what 'scope' values return and operator restrictions, going beyond schema default values.

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?

Clearly states it checks which signals are stale due to upstream data issues. Specifies context: 'Use this before acting on regime, gauges, indicators, or playbooks.' Distinct from sibling tools that fetch specific data.

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?

Explicitly frames when to use ('before acting on...') and explains what stale means. Does not list when not to use or alternatives, but the purpose is clear and contrasted with sibling tools.

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