fetch_applications

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

The description does not reveal any behavioral traits beyond the basic operation. No details on performance, pagination, data size, or side effects. Since no annotations exist, the description carries the burden but only provides minimal information.

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 concise with two sentences: purpose and return type. It is front-loaded and avoids unnecessary detail, though a brief note on usage context would improve it.

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 parameters and an existing output schema, the description is minimally adequate. However, it lacks context about when to use this tool vs siblings and does not hint at the output schema's richness.

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 no parameters, so schema coverage is 100% trivially. The description adds no parameter semantics, but none are needed. Baseline for 0 parameters is high.

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 'Fetch all available applications from the system,' specifying the verb (fetch), resource (applications), and scope (all). It effectively distinguishes itself from siblings like get_application_info (single app) and get_applications_for_tag (filtered).

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 get_applications_for_tag. The description lacks context about use cases, performance implications, or exclusion criteria.

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