get_project_work_package_context

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

No annotations are provided, so the description must disclose behavioral traits. It does not state that it is a read-only operation (though 'Return' implies read), nor does it mention any side effects, permissions, or constraints. The description lacks details on what 'project metadata' includes or how the type parameter affects behavior.

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 with 15 words, no redundancy, and front-loaded with the key verb and resource. It is efficient, though it could be expanded slightly without losing conciseness.

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?

With 2 parameters (0% schema coverage) and no annotations, the description is insufficient for an agent to confidently select and invoke the tool. It lacks details on parameter format, what 'project metadata' encompasses, and when to use this over siblings. An output schema exists but does not compensate for the lack of parameter and behavioral context.

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?

Schema coverage is 0%, so the description must compensate. It says 'for a given type' implying the type parameter selects the schema, but does not explain the project parameter (e.g., ID vs name) or the default behavior when type is null. The description adds minimal meaning beyond the schema itself.

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 it returns 'project metadata' and optionally 'the writable work-package schema for a given type', which identifies the specific verb and resource. However, it does not differentiate from sibling tools like get_project or get_type that may return similar data.

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 explicit guidance on when to use this tool versus alternatives. While it implies usage for combining project metadata and type schema, it does not mention when not to use it or suggest sibling tools like get_project or get_type.

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