assets

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

With no annotations, the description carries the full behavioral burden but discloses nothing: not whether invocation is read-only, what it returns, whether it requires a project context, or what 'can be placed' implies operationally. The phrase 'can be placed' weakly hints these are usable resources, but no concrete behavior is stated.

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 is a single short, front-loaded sentence with no filler, which is appropriate size-wise. However, its brevity comes from under-specification rather than from an efficient statement of a complete idea.

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 parameterless tool the description is the only source of meaning, yet the agent learns neither the return shape nor what invocation does. With no output schema and no annotations, the fragment leaves the core behavior undefined.

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, so there is no parameter semantics to document; baseline 4 applies. The empty schema is consistent with the description, which also implies no inputs.

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 text is a noun fragment ('Media in the project that can be placed') with no verb, so the agent cannot tell whether the tool lists, retrieves, or selects assets. It adds a qualifier beyond the name 'assets' but does not distinguish this tool from siblings help, show, and run.

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 when-to-use, prerequisite, or alternative is mentioned. There is no indication of how 'assets' relates to 'show' or 'run', so the agent must guess when this tool is the right choice.

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