hamravesh_get_app

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

No annotations exist, so the description is the only source. It discloses the masking behavior of env values by default and how 'reveal_secrets' controls it, but does not mention other behavioral aspects like authentication requirements, rate limits, or side effects.

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 a single efficient sentence that front-loads key information (what is returned) and adds the masking behavior. No unnecessary words, but could be slightly more structured (e.g., using separate sentences).

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?

The tool has 3 parameters and no output schema. The description covers the return fields (env, domain, etc.) and the masking behavior, but does not explain the 'org' parameter or the exact return structure. It is adequate but has clear gaps.

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 coverage is low (33%), with only 'reveal_secrets' having a description in the schema. The description provides additional context for 'reveal_secrets' but does not clarify 'app_id' or 'org', leaving ambiguity. Given the low coverage, the description should compensate better.

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 clearly states the tool retrieves full details of an app, listing specific fields (env, domain, resources, build, status). While it doesn't explicitly distinguish from siblings like 'hamravesh_list_apps' or 'hamravesh_app_builds', the purpose 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 implies usage when full app details are needed, but it provides no explicit guidance on when to use this tool versus alternatives, nor any conditions or prerequisites.

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