vebetter_get_app_info

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

With no annotations, the description carries full responsibility for behavioral disclosure, but it only says 'Get information' with no details on return format, side effects, read-only nature, or error handling. This gives the agent no insight into what the tool actually does beyond the implied get operation.

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 sentence and thus concise, but it is under-specified and merely expands the tool name without adding value. The sentence does not earn its place because it repeats information already contained in the tool name, lacking any substantive content.

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 no output schema, no annotations, and a description that provides no information about return values, usage examples, or behavior. An agent cannot determine what data will be returned or how to handle the response. This is extremely incomplete for even a simple get 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 input schema has 100% coverage for its single parameter 'appId', described as 'VeBetter App ID'. The description does not add further meaning to this parameter, but the schema already provides sufficient semantic context. Since schema coverage is complete, a baseline score of 3 is appropriate.

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 'Get information about a VeBetter app' essentially restates the tool name 'vebetter_get_app_info' without adding any specificity about what 'information' entails. It does not differentiate from other get-type tools beyond naming the resource, which is already present in the tool name. This borders on tautology.

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 provides no guidance on when to use this tool versus alternatives. It does not mention prerequisites (like having an appId), what scenarios call for this tool, or any exclusions. There is no context distinguishing it from sibling tools that also retrieve data.

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