get_application

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

With no annotations, the description bears the full burden of disclosing behavioral traits. It mentions the tool returns 'all text file content' but does not indicate whether this is a read-only operation, the size of potential data, authorization requirements, or any 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 very short (two sentences plus argument list) and front-loads the main action, but the brevity comes at the cost of clarity. The structure is minimal yet functional.

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?

Despite having an output schema, the description lacks essential context: it does not define what an 'application' is, how the 'company' parameter maps to an application, or what kind of text file content is returned. For a tool with ambiguous purpose, this is insufficient.

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?

There are 2 parameters with 0% schema description coverage. The description only provides examples for the 'company' parameter ('e.g. "stripe", "Anthropic"') but does not explain the purpose or format of 'workspace_dir'. The meaning of 'company' in relation to 'application' is also unclear.

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 states 'Get all text file content for one application' but the sole required parameter is 'company', which creates confusion about what the tool actually retrieves. It does not clearly specify what constitutes an 'application' or why a company name is needed, and it fails to distinguish itself from siblings like read_application_file or list_applications.

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 such as read_application_file or list_applications. There is no mention of prerequisites, limitations, or scenarios where this tool should be avoided.

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