get_app

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

No annotations provided, so description carries full burden. States it 'gets' metadata, implying a read operation, but does not explicitly confirm read-only nature, authentication needs, rate limits, or absence of side effects. Adequate but could be more explicit.

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?

Single sentence of 13 words, front-loaded with action and key fields. No redundant information. Every word earns its place.

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 only one simple parameter (fully described in schema) and no output schema, the description provides the essential fields but does not specify the response structure or whether all listed fields are guaranteed. Slightly incomplete for an agent that needs to parse results.

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% (app_id has a description 'The app id.'). Description adds no extra meaning beyond schema; does not explain where to find the app_id or its format. Baseline 3 applies since schema already covers param documentation.

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 the verb 'Get', resource 'one Kleap app's metadata', and lists specific fields (status, slug, production_url, published state). Distinguishes from sibling tools like list_apps (multiple apps) and get_publish_status (specific subset).

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 explicit when-to-use or when-not-to-use guidance. Implied usage for retrieving a single app's metadata, but lacks differentiation from list_apps or get_publish_status. With 12 sibling tools, alternative scenarios should be mentioned.

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