postPageAttachments

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

With no annotations, the description should disclose behavioral traits such as side effects (creating attachments), permission requirements, or idempotency. It only covers how files are identified, omitting critical behavioral context.

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 very short but fails to include the primary purpose. Conciseness should not come at the expense of completeness; the single sentence is insufficient and lacks front-loaded clarity.

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 the complexity of the tool (POST with multiple parameters, many sibling tools), the description is severely lacking. It does not explain return values, error conditions, or how to structure the request beyond a vague link.

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 4 parameters, but only 'requestBody' has a description ('Attachment meta data and file data.'). The description's mention of 'order' and 'lid' likely relates to requestBody content but adds no concrete semantics; parameters like 'projectId', 'spaceId', and 'pageName' are left entirely undocumented.

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 does not explicitly state that this tool creates or adds attachments to a page. It only mentions file identification methods (order or lid attribute), leaving the primary action implied. The tool name 'postPageAttachments' suggests the purpose, but the description itself fails to clarify.

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 provided on when to use this tool versus sibling tools like 'postDocumentItemAttachments' or 'postTestRecordAttachments'. There is no indication of prerequisites or alternatives.

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