get_certificates

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false. The description adds value by detailing pagination (limit 20), sorting order, the AND combination of query parameters, and the requirement of at least one filter. These details go beyond the annotations.

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 front-loaded with the action 'Get certificates' and a summary line. It includes relevant details in a structured way, though it could be slightly more concise. The header with emoji and HTTP method adds clarity.

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 the complexity (3 optional params, pagination, sorting) and no output schema, the description covers pagination behavior, sorting, and filter logic. However, it lacks details on the certificate object structure and has a minor typo ('most recently created user' instead of 'certificate'), which slightly reduces completeness.

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?

Input schema coverage is 100% with good descriptions for each parameter. The description adds context that multiple parameters are combined with AND logic and that at least one is required, but it does not elaborate on individual parameter semantics beyond the schema. Baseline is 3, and the added value is marginal.

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 certificates' and specifies it returns a sorted, paginated list of certificates. It uses a specific verb and resource, and distinguishes itself from sibling tools as the only certificate-specific getter.

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 clear context: it lists certificates sorted by most recently created, paginated with a limit of 20, and requires at least one query parameter. It explains that multiple filters are combined with AND logic. However, it does not explicitly state when not to use this tool or compare to alternatives.

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