policy_get_by_id

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

With no annotations provided, the description carries the full burden of behavioral disclosure. 'Get Policy by Id' implies a read operation, but it does not explicitly state read-only behavior, auth requirements, rate limits, or error handling (e.g., if policy not found). The minimal description is insufficient for transparency.

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 concise at 4 words and front-loaded with the core purpose. Every word is necessary, but it could be slightly more informative without being verbose. It earns its place but borders on under-specification.

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 and simple parameters, the description lacks completeness. It does not explain what is returned, behavior on missing policy_id (all parameters optional), or prerequisites. For a tool with many siblings, more context is needed for correct usage.

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?

The input schema has 67% description coverage (organization_id and override_organization_id have descriptions), but the tool description adds no parameter semantics. It does not mention that policy_id is optional or clarify the relationship between parameters, so no added value beyond the schema.

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 verb 'Get' and the resource 'Policy by Id', distinguishing it from sibling tools that target different entities (e.g., application_get_by_id, tag_get_by_id). However, it is minimal and does not clarify what 'Policy' refers to, limiting full clarity.

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 provides no guidance on when to use this tool versus alternatives like similar get_by_id tools for other resources or get_by_parameters tools. There is no mention of when-not-to-use or specific context, leaving the agent without decision support.

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