list_worker_profiles

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

Annotations already declare readOnlyHint=true, so the description is not required to state that. It adds context about the optional reload behavior, but does not explain what reload does (e.g., side effects on the displayed list or underlying data). This is a moderate addition beyond 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 a single sentence that front-loads the core purpose and then adds the optional behavior. There is no redundancy or filler, making it highly concise and well-structured.

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 tool's simplicity (one optional boolean parameter), the presence of an output schema, and annotations covering read-only behavior, the description is complete enough. An agent can invoke this tool correctly without missing critical information.

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 only defines 'reload' as a boolean with default false, and schema description coverage is 0%. The description explicitly mentions 'optionally reload TOML files', which explains the parameter's purpose and adds meaning beyond the raw schema. This is a clear compensation for the missing schema description.

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 the verb 'List' and the resource 'declarative worker profiles and capabilities', and mentions an optional reload behavior. It is distinct from sibling tools which all relate to jobs and results, so there is no ambiguity about its purpose.

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 gives a hint about when to use the reload option ('optionally reload TOML files') but does not explicitly contrast this tool with alternatives or state when not to use it. Since siblings are clearly job-related, usage is implied, but no direct guidance is provided.

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