list_profiles

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description adds no behavioral context beyond that – no mention of size, filtering, pagination, or what 'labelled historical evidence' refers to operationally.

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?

It's a single short sentence, which is appropriately sized, but half of it ('precisely labelled historical evidence') carries no clear meaning and reads as filler rather than front-loaded substance.

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?

An output schema exists, so return values needn't be explained, and the annotations cover the safety profile. However, for a list/grounding tool whose value depends on an agent understanding what 'profiles' and 'evidence' mean in this domain, the description leaves a meaningful conceptual gap.

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 and the schema coverage is 100%, so there is nothing for the description to compensate for. Baseline 4 applies.

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 verb is 'List' and the resource is 'game profiles', which is reasonably clear, but the trailing clause 'precisely labelled historical evidence' is opaque – it's unclear whether this returns evidence records, evidence metadata, or something else. The sibling tools (get_job, inspect_iso, etc.) don't overlap conceptually, so no differentiation is strictly needed, but the tool's actual output purpose remains ambiguous.

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 on when to call this tool, what prerequisites exist, or what alternatives might apply. It's a discovery-style list tool so an agent can infer 'call this to enumerate profiles', but nothing is stated explicitly.

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