health-stats

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

No annotations provided, so description must fully disclose behavior. It indicates a read operation but does not specify any behavioral traits such as authentication requirements, data freshness, or whether the call is expensive. Only basic purpose is communicated.

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?

Single sentence with a tag is very concise and front-loaded. However, the inclusion of '(Tags: Health)' is somewhat extraneous and not structurally ideal, but it does not detract significantly.

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?

While the tool is simple (0 params, no output schema), the description only lists a few examples of statistics. An agent would benefit from knowing the structure or format of the returned data, which is missing. Adequate but not fully complete.

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?

Tool has zero parameters, making schema coverage 100%. The description adds nothing beyond the schema, but baseline for zero params is 4. No further info needed.

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?

Description clearly states it 'Returns statistics about the application' with examples (workspaces, users, cards). This is a specific verb+resource. However, it does not differentiate from sibling 'health-health' which might also provide health-related data.

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 on when to use this tool versus alternatives like 'health-health' or other read tools. The agent must infer usage from the name and description alone.

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