project_get_metadata

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

No annotations are provided, so the description must carry the behavioral disclosure burden. It does disclose one important non-obvious behavior: the 'year' field defaults to '2018' for new projects, which is a stale template default rather than the current date. However, it does not mention return format, error behavior, or assumptions about an open project, leaving several behavioral aspects undisclosed.

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 two sentences with no filler. The first sentence states the core operation and result fields, and the second provides a high-value implementation quirk about the 'year' default. Every sentence earns its place.

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 zero-parameter getter with no output schema, the description is largely complete: it identifies the tool's result fields and flags a surprising default value. It could be more complete by describing the structure of the returned metadata or noting whether it requires an open project, but those are minor gaps given the tool's simplicity.

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 the schema coverage is 100%, so there is no parameter burden to compensate for. The description adds meaningful semantics by naming the metadata fields returned, which is useful context beyond the empty input schema.

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 uses a specific verb and resource: 'Get project metadata tags' and then enumerates exactly which fields are returned (artist, track title, album, track number, year, comments). This makes the tool's purpose unmistakable and distinguishes it from generic project tools like project_get_info.

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 implies the tool is used when reading project metadata tags, but it does not explicitly state when to prefer this over siblings such as project_get_info or project_set_metadata. There is no 'use this instead of...' guidance, so the usage context is only implied rather than explicitly routed.

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