list_subjects

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

The description itself adds no behavioral detail beyond the tool name. However, annotations already declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint=false, so the most important behavioral guarantees are covered elsewhere; there is no contradiction.

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 extremely concise and front-loaded, with no wasted words. It could be slightly more informative by saying 'Returns all subjects', but for a zero-parameter list tool this length is appropriate.

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 low complexity, rich annotations, and presence of an output schema, the description is sufficiently complete. It does not explain what 'subjects' means or mention pagination/ordering, but these are not critical for such a simple parameterless list operation.

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 has zero parameters and schema coverage is 100%, so there is nothing for the description to clarify. The baseline of 4 applies because no parameter documentation is needed.

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 states the exact operation and resource: 'List Subjects'. It is distinguishable from the many sibling list_* tools because no other sibling targets subjects, so an agent can select it without needing to inspect schemas.

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?

Usage is implied rather than explicit: an agent can infer 'use this when a list of subjects is needed', but the description does not state this directly or mention any situations where a sibling tool should be preferred. Since there are no sibling subject tools, the ambiguity is low.

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