Api pmbok accreditations list

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

Annotations already declare readOnlyHint=true, idempotentHint=true, openWorldHint=true, and destructiveHint=false, so basic safety is covered. The description adds only an internal serializer-context note and no user-relevant behavior such as pagination, permissions, filtering, or response behavior.

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 single sentence is short but focuses on implementation rather than the task, making it under-specified rather than efficiently concise. There is no front-loaded statement of the action, scope, or return values.

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 14-parameter list endpoint with no output schema and zero schema descriptions, this definition is far too thin for an agent to call it correctly. It lacks filtering, pagination, ordering, and any indication of what PMBOK accreditation data is returned.

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?

There are 14 parameters with 0% schema description coverage, and the description names none of them nor explains filters such as status, category, author, folder, or ordering. Since the schema itself is untyped and undocumented, the description completely 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 never states that the tool lists PMBOK accreditations or what data it returns; it describes an internal implementation detail ('Override the list method to inject optimized data into the serializer context'). An agent cannot infer the user-facing purpose from this text, even though the tool name hints at a list endpoint.

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?

There is no guidance on when to use this list endpoint versus alternatives such as other PMBOK list/retrieve endpoints, and no explanation of filters, exclusions, or prerequisites. The description gives an agent no basis for choosing this tool over siblings.

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