list_schemas

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

readOnlyHint=true already tells the agent this is a safe read. The description adds that the endpoint is fixed/server-capability, meaning results are static and unfiltered, which is genuinely useful context. It does not, however, describe response shape or pagination, so it is a modest rather than rich addition.

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 compact sentences, front-loaded with the action and resource, with the second sentence adding the only non-obvious fact. Nothing is wasted.

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?

For a no-parameter, read-only discovery endpoint with no output schema, the description tells the agent what is returned (core schemas and vendor extensions) and that it is static. That is sufficient; only the concrete return format is unstated, which is minor.

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 tool takes zero parameters, so the baseline is 4. The description correctly implies there is nothing to configure by calling it a fixed capability endpoint, and the empty schema confirms this.

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?

States a specific verb (List) and resource (SCIM schemas), and names the scope: core schemas plus Beyond Identity extensions. It does not explicitly differentiate from the closely related discovery sibling list_resource_types, so it falls short of a 5.

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 'fixed server-capability endpoint' implies this is a static discovery call with no filtering, which hints at when to reach for it, but there is no explicit when-to-use guidance or comparison to list_resource_types or get_service_provider_config.

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