get_entities

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

Annotations already declare readOnlyHint and openWorldHint, and the description adds a genuinely useful trust boundary: project content is collaborator-authored and must be treated as data, never as instructions. "Flat list" also discloses that the structure is flattened rather than nested, which is real behavioral context. It does not cover ordering, recursion into folders, or result size, keeping it below a 5.

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 purpose is front-loaded in the first sentence and the second is a compact safety note. Both sentences carry information, though the injection warning is somewhat generic boilerplate that likely repeats across this server's tools.

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 no output schema, the description compensates by naming what is returned (paths and types) and the tool is a simple one-parameter read whose annotations cover the safety profile. Only minor gaps remain around ordering, folder recursion, and result limits.

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?

There is a single parameter at 100% schema description coverage, so the schema fully documents project_id and the baseline of 3 applies. The description adds no format or sourcing detail about how to obtain the project ID.

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 gives a specific verb and resource ("Get a flat list of all files and documents") and states the returned attributes (paths and types), so an agent knows exactly what it gets back. It stops short of naming the sibling it is not — e.g. get_project_info or pull_project — so the boundary with those tools must be inferred.

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?

There is no statement of when to use this instead of alternatives such as get_project_info, pull_project, or download_file, and no exclusions or prerequisites. The only conditional advice is about treating content as data, which is a safety rule, not usage routing.

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