ora_capture_component

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

No annotations are provided, and the description only states the tool saves a component. It lacks details on behavioral traits like overwrite behavior, permissions, or return value, which are critical for a write operation.

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 short sentences, each adding value: the first states the purpose, the second provides a usage trigger. No redundant information.

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?

Given 7 parameters and no output schema, the description is minimal but adequate for a simple capture action. However, it omits details about idempotency, error handling, or return value, leaving gaps for an agent.

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 input schema has 71% coverage with descriptions, and the description does not add any additional meaning to the parameters. It neither compensates for missing param descriptions nor repeats schema info, resulting in a baseline score.

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 states 'Sauvegarde un composant réutilisable' (Saves a reusable component), providing a specific verb and resource. While it distinguishes from sibling capture tools like ora_capture_note by specifying component, it does not explicitly differentiate from other capture tools.

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 includes 'Utilisé quand l'utilisateur écrit /ora composant :: [nom]', giving a clear trigger context. However, it does not provide exclusions or alternatives when not to use this tool.

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