fcp_share

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

No annotations provided. The description only notes that an empty destination opens the default, but fails to disclose whether the operation is synchronous, asynchronous, or what happens to the app state during export.

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 extremely concise with a clear structure: one line for purpose and one line for the parameter. No unnecessary text.

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 simple tool with one parameter and an existing output schema, the description lacks context about prerequisites (e.g., listing destinations) and potential side effects, making it only minimally complete.

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 parameter 'destination' has no schema description, but the description adds context (share destination name, default behavior). This partially compensates for 0% schema coverage, but could reference fcp_list_share_destinations.

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 the tool triggers a share/export from FCP, with a specific verb and resource. It distinguishes from siblings like fcp_export_xml, but could be more explicit about the type of export.

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 on when to use this tool vs alternatives, such as fcp_list_share_destinations for listing destinations. No prerequisites or exclusion criteria mentioned.

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