get_site_reliability

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

No annotations are provided, so the description carries the full burden of disclosing behavior. It simply states it 'gets' a score, but does not mention authentication requirements, error handling, or what constitutes a reliability score. This lack of detail hinders the agent from understanding potential side effects or constraints.

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 is concise and front-loaded with the action and resource. However, it could be slightly expanded to include context without losing conciseness.

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 the absence of an output schema and annotations, the description should provide more context about what the reliability score represents (e.g., format, range). It also does not specify return values or edge cases, making it incomplete for the AI agent to understand the full behavior.

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 100% (the parameter 'site_id' has a description 'Site ID' in the schema). The description adds no additional meaning beyond the schema, but since the schema already covers the parameter, a 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 states the verb 'Get' and the resource 'reliability score for a site' clearly. However, it does not distinguish from the sibling tool 'get_asset_reliability', which also provides reliability scores; a more specific description could mention that this is for sites as opposed to assets.

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?

There are no guidelines on when to use this tool versus alternatives like 'get_asset_reliability' or other retrieval tools. The description does not mention any context or prerequisites, leaving the AI agent without guidance on tool selection.

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