get_policy_by_name

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

The description claims 'get details' but does not disclose the optional 'include_deleted' parameter's behavior or that the tool is read-only. With no annotations, the agent lacks expected side-effect information.

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 short but adequately structured for a simple tool. However, it is too terse given the number of parameters, sacrificing clarity for brevity.

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?

The description fails to cover optional parameters and does not specify the return value. For a tool with no output schema, more detail is needed to ensure correct 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?

With 0% schema coverage and 3 parameters, the description only clarifies the 'name' parameter implicitly. 'fields' and 'include_deleted' are not explained, leaving the agent uninformed about their usage.

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 action (get details) and resource (policy by name). However, it does not differentiate from the sibling tool 'get_policy', which may fetch by ID, leaving ambiguity for the agent.

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?

No guidance is provided on when to use this tool versus alternatives like 'list_policies' or 'get_policy'. No prerequisites or exclusions are mentioned.

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