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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds useful scope context by clarifying that it reports current availability/policy and that runtime evidence is separate, but it does not disclose permissions, freshness guarantees, or other behavioral details beyond that.

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 efficient sentence with no wasted words, and the key scoping distinction is front-loaded. It is slightly cryptic and would benefit from one more clause defining 'serve decision', but it is structurally sound.

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?

An output schema exists, so return-value details need not be covered, and annotations handle the read-only profile. However, for a getter whose name suggests a 'serve decision', the description remains vague about what is actually returned and does not clarify the required 'id' parameter, leaving the definition only minimally 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?

With schema description coverage at 0%, the single required 'id' parameter is undocumented in both the schema and the description. The description mentions 'file availability' but does not indicate whether 'id' refers to a file, request, or serve decision, leaving a meaningful semantic 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?

The description gives a specific verb and partial resource ('Read current file availability and policy'), but the tool name 'get_serve_decision' implies a decision object, and the description never clearly defines what a 'serve decision' is. It hints at scope by saying runtime evidence is separate, but does not differentiate from siblings like get_artifact or list_files.

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 phrase 'runtime evidence is separate' provides a weak exclusion, but there is no explicit when-to-use guidance, no stated preconditions, and no named alternatives among the many sibling tools. An agent must infer when this tool is appropriate.

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