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

With no annotations, the description carries the full burden for behavioral disclosure. It implies an informational/status query but does not explicitly say it is read-only, what data it returns, whether authentication is needed, or what side effects may occur.

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 and contains no filler, making it easy to parse. However, it is a fragment rather than an action sentence, and converting it to something like 'Get the current Onsite plan and remaining credits' would improve structure.

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?

For a zero-parameter tool this is nearly adequate: the agent knows the domain and expected content. But with no output schema and no annotations, the description should state the retrieval semantics more explicitly to be fully self-sufficient.

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 takes zero parameters, so the baseline is 4. The description adds no misleading or unnecessary parameter information; 'Onsite plan and remaining credits' hints at what the response will cover.

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 is a noun phrase and contains no verb indicating what the tool does, so an agent must infer that it retrieves or displays the Onsite plan and remaining credits. It at least names a distinct resource (credits/plan) that separates it from event/company/search siblings.

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 when-to-use guidance is provided. The description never mentions alternatives, prerequisites, or situations where this tool should be chosen over siblings such as get_company or get_event.

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