authentication_settings_get_metadata

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

No annotations are provided, so the description carries the burden. It discloses the permission requirement and the endpoint, and the verb 'Get' implies read-only. However, it does not describe the response format, rate limits, or side effects, which is a gap for a no-annotation tool.

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 brief, front-loaded with the primary purpose, and includes only necessary context (permissions, endpoint, example). No redundant wording.

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 tool is simple and the description covers purpose, permissions, and an example request. However, without an output schema, it does not describe what metadata is returned, and no pagination or response details are given. For a basic read endpoint this is adequate but not fully 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?

The schema has a single 'request_data' parameter with no documented properties and additionalProperties true. The description provides only an example with an empty object, adding no semantic meaning about what request_data should contain. Since schema coverage is 0%, the description fails to compensate.

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 'Get IdP metadata' and 'Get the metadata for all IdPs', specifying the verb, resource, and scope. This distinguishes it from sibling tools like authentication_settings_get_settings.

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 context that this endpoint requires Instance Administrator permissions and uses a specific POST endpoint. However, it does not explicitly discuss when to use this over alternatives or mention exclusions, so it is clear but not fully explicit.

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