tier_zero

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

There are no annotations, and the description does not disclose whether the operation is read-only, what it returns, or any side effects. The default Cypher query suggests a read operation, but the description itself provides no behavioral information.

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 text is short but under-specified. It consists of a vague phrase and a parenthetical note, neither of which conveys essential functional information. This is under-specification, not effective 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 no output schema and no annotations, the description should explain return values and usage context. It only provides a label and a verification note, leaving the agent without enough information to invoke the tool correctly, especially given similar sibling tools.

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 description coverage is 0%, and the description does not explain the parameters k and cy or their purposes. The defaults are visible in the schema, but the description adds no meaning to help an agent understand or configure the query.

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 'Tier-0 objects' restates the tool name without specifying an action such as 'list' or 'get'. It mentions the CE label Tag_Tier_Zero but does not clarify what the tool does, making it hard to distinguish from siblings like paths_to_tier0.

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 guidance is given on when to use this tool versus alternatives such as run_cypher or paths_to_tier0. The parenthetical 'requête vérifiée' (verified query) hints at pre-validated logic but does not explain use cases or exclusions.

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