list_applications

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint, and the description's 'Read Application' merely restates the read-only nature without adding new behavioral context. It does not mention return shape, pagination, authentication, or any side effects beyond what annotations cover. No contradiction with annotations.

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 extremely short, with no filler words. The endpoint is front-loaded after the brief purpose, making it easy to scan. However, the phrase 'Read Application' is terse and could be more informative without length cost.

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?

With zero parameters, an output schema present, and annotations covering safety, the description plus structured data is sufficient for invocation. The only missing piece is an explicit statement that this returns all applications, but the endpoint path and tool name supply that context. Overall complete for a simple list operation.

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?

The tool has zero parameters, so the schema fully covers inputs. The description adds no parameter details, but none are needed. Baseline of 4 for no-parameter tools applies.

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?

States 'Read Application' and provides the exact endpoint GET /api/v1/applications, making verb and resource clear. The plural path and tool name distinguish it from get_applications_by_id and list_applications_schema, though it never explicitly says 'list all applications'. Thus it is clear but leaves a small ambiguity.

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 offers no guidance on when to use this tool versus alternatives such as get_applications_by_id or list_applications_schema. There is no mention of use cases, exclusions, or relation to sibling tools. This is a significant gap.

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