get_active_tfrs

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

With no annotations, description discloses return contents (TFRs containing point and nearby within radius, including times and descriptive text). Does not discuss side effects or permissions, but read-only nature is implied.

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 sentences, no wasted words. Purpose is front-loaded, and the alternative is succinctly mentioned.

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 no output schema, three simple parameters, and no annotations, the description adequately covers what the tool does and returns. It references a sibling for extended need.

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 baseline is 3. Description adds context about 'near a location' and returned fields but does not significantly extend parameter meaning beyond schema.

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?

Description clearly states the verb 'List', the resource 'active Temporary Flight Restrictions (TFRs)', and the scope 'near a location'. It differentiates from sibling 'check_airspace' by recommending it for a full assessment.

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 advises using 'check_airspace' for a full multi-layer assessment, implying this tool is for active TFRs only. Does not provide negative usage cases but is adequate.

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