policy_load_info

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

Declares the tool as read-only and describes return values. No annotations provided, so the description carries full burden. Adequately discloses behavior for a simple info tool, though does not mention authentication or other potential traits.

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?

Two concise sentences. First sentence states functionality, second gives usage guidance. Every sentence earns its place with no redundancy.

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 no output schema, description adequately explains return values (path, count, version). Usage context provided. Tool complexity low, description is complete for its purpose.

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?

No parameters exist, schema coverage is 100%. Description adds no param details, but baseline for zero-param tool is 4. No need for further explanation.

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 clearly states the tool reports the policy file path, rule count, and schema version. It uses specific verb 'Report' and resource 'policy file loaded by this server'. Distinguishes from siblings like policy_evaluate and policy_list_rules.

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?

Explicitly suggests using it once at session start to confirm expected policy. Does not state when not to use it or name alternatives, but context from siblings implies it's for initial verification.

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