get_config

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

No annotations are provided, so the description must fully disclose behavioral traits. It only states the action 'Get current configuration' without any details on permissions, rate limits, side effects, or return format. This is inadequate for a tool with potential read operations and no output schema.

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 a single sentence 'Get current configuration', which is front-loaded and wastes no words. However, this brevity contributes to underspecification rather than clarity.

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 annotations, no output schema, and low parameter coverage, the description is incomplete. It does not explain what 'configuration' entails, how results are returned, or behavioral aspects, making it insufficient for effective tool use in a context with many sibling tools.

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 input schema has one parameter 'section' with 0% description coverage and no enums. The description does not mention parameters at all, failing to compensate for the lack of schema documentation. It should explain what 'section' refers to (e.g., a configuration category) to add semantic value.

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 'Get current configuration' restates the tool name 'get_config' with minimal elaboration, making it tautological. It specifies the verb 'Get' and resource 'current configuration' but lacks detail on what configuration refers to (e.g., system, application, or Airflow-specific settings), failing to distinguish it clearly from sibling tools like get_variable or get_connection.

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 does not mention context, prerequisites, or comparisons to sibling tools (e.g., get_variable for specific values or get_connection for connection details), leaving the agent without usage direction.

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