alterios_project_health

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

With no annotations provided, the description bears full burden. It states 'read-only', indicating no side effects, but does not disclose other behavioral traits such as auth requirements, rate limits, or performance characteristics. Adequate but not rich.

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 that front-loads the purpose. It is concise with no wasted words, though it could be structured to include more detail without becoming verbose.

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 8 parameters with no descriptions, the tool is not fully usable without external knowledge. The output schema exists but the description fails to explain how to use parameters correctly, making it incomplete for effective invocation.

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?

Schema description coverage is 0% and the description adds no information about the 8 parameters (e.g., profile, refresh, use_cache). It provides zero additional meaning beyond the schema, which is a significant gap.

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 'Return a read-only health summary for forms/views/scripts/BPMN/reports' with a specific verb and resources. The phrase 'before writes' distinguishes it from sibling read tools and emphasizes its role as a pre-write health check.

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 explicitly says 'before writes', indicating this tool should be used prior to performing write operations. However, it does not mention when not to use it or provide explicit alternatives, so guidance is clear but limited.

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