App Config

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

With no annotations provided, the description carries the full burden and handles it well. It explicitly states 'Side effects: none (read-only)' and discloses that secret-looking keys are masked unless reveal_secrets=True is passed. These are meaningful behavioral traits that go beyond what the schema alone conveys.

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?

Three short sentences, each earning its place: the core purpose, the read-only side effect, and the secret-handling behavior. The most important action is front-loaded, and there is no filler or redundant repetition of schema information.

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?

For a two-parameter read-only tool with an output schema, the description is complete. It covers the resource scope, side-effect profile, secret masking behavior, and the key parameter behavior. There is nothing essential missing for an agent to select and call this tool correctly.

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 0%, so the description must compensate. It references the app parameter via 'for a Dokku app' and explains reveal_secrets by describing the masking behavior and its dependency on explicitly passing True. It could be slightly more explicit about the app parameter meaning, but it adds real semantic value beyond the bare 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?

The description opens with a precise verb and object: 'Get environment config vars for a Dokku app.' This makes the tool's read-only retrieval purpose immediately distinguishable from siblings like set_config and create_app. The scope is clear and specific.

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?

The description clearly signals this is the retrieval tool for app config values, especially with 'Get' and the explicit 'read-only' note. It gives conditional guidance for reveal_secrets, but it does not explicitly name alternatives or state when not to use it, so it falls short of full routing guidance.

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